[esb-issues] [JBoss JIRA] Commented: (JBESB-3275) SOAPClient may fail NTLM negotiations
Magesh Kumar B (JIRA)
jira-events at lists.jboss.org
Fri Jun 25 03:16:47 EDT 2010
[ https://jira.jboss.org/browse/JBESB-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12537025#action_12537025 ]
Magesh Kumar B commented on JBESB-3275:
---------------------------------------
Unable to replicate it locally. All requests are sent as HTTP/1.1 (http://www.io.com/~maus/HttpKeepAlive.html) and Keep-Alive is by default.
DEBUG [org.apache.commons.httpclient.HttpMethodBase] Resorting to protocol version default close connection policy
DEBUG [org.apache.commons.httpclient.HttpMethodBase] Should NOT close connection, using HTTP/1.1
When using a proxy the keep-alive is sent
DEBUG [httpclient.wire.header] >> "User-Agent: Jakarta Commons-HttpClient/3.0.1[\r][\n]"
DEBUG [httpclient.wire.header] >> "Host: xxx.xxx.x.xx[\r][\n]"
DEBUG [httpclient.wire.header] >> "Proxy-Connection: Keep-Alive[\r][\n]"
> SOAPClient may fail NTLM negotiations
> -------------------------------------
>
> Key: JBESB-3275
> URL: https://jira.jboss.org/browse/JBESB-3275
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Services
> Affects Versions: 4.7
> Reporter: Kevin Conner
> Assignee: Magesh Kumar B
> Fix For: 4.9
>
>
> The soapui client may fail NTLM negotiations if no keep-alive is set on the connection.
> Some servers may respond with a directive to close each connection, which soapui honours. If this happens then each step of the NTLM negotiation will be handled over a separate connection and will fail.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the esb-issues
mailing list