:39
To: Commons HttpClient Project
Subject: RE: question re: cookies
Ah yes, cookie headers that were manually set used
to get overridden. As far as I remember, that changed
a while back. Though I cannot tell whether the change
went into 2.0 or only into the development branch.
cheers,
Roland
HttpClient Project
[EMAIL PROTECTED]
cc:
Subject:RE: question re: cookies
Gil, Roland
Pluggable cookie policies as well as ability to manually set cookie
headers are supported in the development branch only. For 2.0 there is no
way around forking HttpClient
Oleg
reason
why the cookie is set with that path.
cheers,
Roland
Alvarez, Gil [EMAIL PROTECTED]
25.03.2004 07:37
Please respond to Commons HttpClient Project
To: [EMAIL PROTECTED]
cc:
Subject:question re: cookies
Hi, we're porting some old code to use
: Roland Weber [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 24, 2004 10:51 PM
To: Commons HttpClient Project
Subject: Re: question re: cookies
Hello Gil,
two options. If you only need to get the cookie for
your application, then access the header directly
instead of looking into the http state
to Commons HttpClient Project
To: Commons HttpClient Project
[EMAIL PROTECTED]
cc:
Subject:RE: question re: cookies
Thanks, yes, the old code pulled it out of the header directly, but the
rest of the story is that I save that cookie for later submittal
