On Fri, 2007-02-02 at 17:52 +0200, Eugeny N Dzhurinsky wrote: > On Fri, Feb 02, 2007 at 02:35:43PM +0100, Oleg Kalnichevski wrote: > > Hi Eugeny, > > > > Not out of the box. You'll have to implement a custom cookie policy or > > extend an existing one and add some logic to control the maximum cookie > > header length. > > > > Oleg > > Okay, looks like I need to play with CookieSpecBase class. Could you please > tell me, am I correct if I would say there is no way to specify header length > on per-host basis (or for some conditions)? As far as I learned from sources, > CookieSpec implementation is obtained by static method using newInstance, and > there's no way to set a property of the specs somehow. >
Hi Eugeny, The default cookie policies in HttpClient 3.x are stateless and therefore can use executed simultaneously by multiple threads. Presently there is no way around writing a custom cookie policy that somehow maintains a state information on a per host basis internally. HttpClient 4.0 will have statefull cookie policies which can be configured at runtime, but I understand it is a small comfort to you Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
