I'd have to see the raw wire transfers. See:
http://cwiki.apache.org/CXF20DOC/debugging.html
on how to enable them.
Most likely, they AREN'T there. Many web servers, if they get a
JSESSSIONID comming in, they don't send it back. There isn't a point
as they know the client is configured to honor the session and will
keep sending it.
I checked the code and we don't remove anything from the map. The
HTTP_RESPONSE_HEADER map is an exact copy of the map returned from the
HTTPUrlConnection.getHeaderFields() call.
Dan
On Jun 16, 2008, at 4:52 PM, Landslide wrote:
The issue is that the cookie "JSESSIONID" is indeed in the HTTP
header of the
2nd and 3rd responses. That's the only way that the server side can
track
this exact same HTTP session based on its session ID value initially
set by
the server side in the 1st response.
As I mentioned previously, I could see this "JSESSIONID" cookie in
the 2nd
and 3rd incoming requests on the server side since the client indeed
sent
back the whole headers correctly.
If I use the Apache Axis2 (1.3.0), I can retrieve, on the client
side, the
cookie "JSESSIONID" in all 3 responses with the correct value (one
value
only and no change set by the server side).
--
View this message in context:
http://www.nabble.com/CXF-2.1-client-does-not-retrieve-HTTP-session-header-info-correctly-tp17870106p17873057.html
Sent from the cxf-user mailing list archive at Nabble.com.
---
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog
