RE: question re: cookies

2004-03-25 Thread Roland Weber
ient Project" To: "Commons 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

RE: question re: cookies

2004-03-25 Thread Kalnichevski, Oleg
: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

RE: question re: cookies

2004-03-24 Thread Roland Weber
004 08:04 Please respond 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

RE: question re: cookies

2004-03-24 Thread Alvarez, Gil
o. -Original Message- From: 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

Re: question re: cookies

2004-03-24 Thread Roland Weber
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. That's probably what your old code did, right? Otherwise, implement and configure your own cookie policy. Copy the default implementation that b