Alexander, If the word of the RFC 2109 is to be strictly followed, any expiration date which does not conform to the following format must be considered invalid:
Wdy, DD-Mon-YY HH:MM:SS GMT (as defined in infamous Netscape cookie spec draft) HttpClient supports a wide variety of non-standard formats, but not this one. It lacks the time zone bit. Currently, there's no way to specify an alternative set of date formats (apart from tweaking the DateParser and recompiling the whole damn thing). In the future release (currently designated as 2.1) the problem will be addressed. Oleg On Sat, 2003-09-13 at 11:39, Derek Alexander wrote: > Hello, > > I'm getting the following error: > > 13-Sep-2003 12:32:28 org.apache.commons.httpclient.HttpMethodBase > processResponseHeaders > WARNING: Invalid cookie header: "foo=baa; path=/; expires=Sat, 01 Jan 3000 > 00:00:00;". Unable to parse expiration date parameter: Sat, 01 Jan 3000 > 00:00:00 > > And it isn't storing the cookie. > > Am using the following settings: > > client.setStrictMode(true); > client.getState().setCookiePolicy(CookiePolicy.COMPATIBILITY); > > Any suggestions on the easiest way to make it accept that cookie would be > appreciated > > Thanks. > Derek > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
