hc-httpclient-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Riad Souissi" <rsouiss...@stc.com.sa>
Subject Handling of HTTP error code 401
Date Wed, 23 Feb 2005 10:19:51 GMT


In case the HTTPClient is set up to preserve Cookies, I have the
following problem:

- Sometimes, HTTPClient presents a cookie which is not valid anymore in
the target HTTP server (because it timed out, or the server cleaned up
some sessions or the server restarted, etc).
- The HTTP server returns HTTP 401 error code
- The HTTPClient re-attemps to authenticate, but still re-use the same
cookie id.
- All subsequent executes that involve the HTTPConnection which has this
cookie will fail, until the Cookies are expired in the HTTPClient.
- I thought about catching the 401 code on top of the HTTPClient and
cleanup the Cookie my self. The problem is that I do not know which
Cookie ID has a problem and from which HTTPConnection object.

My guess/suggestions is that the HTTPClient could be made to re-set the
Cookie from the HTTPConnection object it is currently using when it
receives HTTP 401 code and it had already provided the correct
Authentication credentials before (which is my case since I use BASIC
and setAuthenticationPreemptive=true).

Any idea/suggestions/comments ?


DiscalimerThe information in this email and in any files transmitted with it,
is intended only for the addressee and may contain confidential and/or privileged material.
Access to this email by anyone else is unauthorized. If you receive this in error,
please contact the sender immediately and delete the material from any computer.
If you are not the intended recipient, any disclosure, copying, distribution or
any action taken or omitted to be taken in reliance on it, is strictly prohibited.
Statement and opinions expressed in this e-mail are those of the sender, and do not
necessarily reflect those of STC.
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message