Eric,
You are not the first one to complain about the problem. I think there's
a fairly easy way of solving it: all we have to do is to ensure that
only only automatically generated 'cookie' headers can ever be
overwritten.
Feel free to file a bug report.
Oleg
On Tue, 2003-08-26 at 03:10, Eri
responses the way a proxy should.
regards,
Roland
Eric Bloch <[EMAIL PROTECTED]>
26.08.2003 03:10
Please respond to "Commons HttpClient Project"
To: Commons HttpClient Project
<[EMAIL PROTECTED]>
cc:
Subject: Re: regression in co
Hi Adrian,
Thanks for the quick response!
My problem is that I don't have a 'Cookie' object. I only have the text
string for the name of the cookie and its value and I couldn't see any
easy way for me to construct up a Cookie object from that... or any
exposed http cookie header (not set-coo
Hi Eric,
> If I manually set a "cookie" header on a request (for example, if I'm
> proxying a request myself), HttpMethodBase will always clobber it during
> addCookieRequestHeader(). I would think that it should merge in any
> client state cookies to the header I add, rather than clobbering mine.
