commons-user mailing list archives

Hi Derek,
Having the server generate a cookie with a standard date format would
probably be the easiest:) This date looks like the RFC 1123 style
format minus the time zone at the end.
Currently (in HttpClient 2.0) the cookie formats are stored in the
DateParser class and can only be modified by editing that class. If
you would like to have another format added to DateParser please post
an enhancement request against HttpClient in Bugzilla.
The problem of static date formats is being addressed in HttpClient 2.1
(currently in pre-alpha development). Code for handing this will be in
CVS HEAD in the next few days.
Mike
On Saturday, September 13, 2003, at 07:39 AM, 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: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org