[esb-issues] [JBoss JIRA] Closed: (JBESB-3275) SOAPClient may fail NTLM negotiations
[
https://jira.jboss.org/browse/JBESB-3275?page=com.atlassian.jira.plugin.s...
]
Magesh Kumar B closed JBESB-3275.
---------------------------------
Resolution: Done
Was able to replicate this finally using a squid transparent proxy on the client side.
When squid is used as a transparent proxy, by default it responds with HTTP/1.0 response
and Connection: close response header. Added keep-alive in EsbWsdlLoader and SOAPClient.
trunk: 33712
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