Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
4.4 Final
-
None
-
None
Description
when responding to initial authentication needed response from a tomcat java web application, "Set-Cookie" header is not processed and put back to the second request as JSESSIONID which results in getting another "Set-Cookie" header on the second response with a differnt seesion id, on the third response, similar scenario happens. is there a way to force response interceptors to run while NTLM handshaking is happening?
Attachments
Issue Links
- duplicates
-
HTTPCLIENT-1451 HttpClient does not store response cookies on a 401
- Resolved