----- Original Message ----
> From: Clinton Gormley <cl...@traveljury.com>
> To: Joe Schaefer <joe_schae...@yahoo.com>
> Cc: Clinton Gormley <cl...@traveljury.com>; apreq-...@httpd.apache.org
> Sent: Monday, February 16, 2009 5:09:46 AM
> Subject: Re: Cookie parsing errors: conflicting information, expected token
> not present
>
>
> > Tell you what I'll do- I'll throw the cookie headers you mentioned earlier
> > into the test suite and see if I can adjust the parser to make better sense
> > of them (no promises tho). What won't change is the error behavior- apreq
> > will throw an error on invalid cookie headers, to alert you that the data
> > in the header is malformed and may not be parsed faithfully. If you still
> > want to work with the data, you can always do that by using the error object
> > as if it were an ordinary APR::Request object.
>
> That's interesting - I didn't know you could do that.
APR::Request::Error is a subclass of APR::Request. What it does differently
from
APR::Request is that it runs all the commands with errors disabled. Most of the
stuff you are worried about would be adequately handled by just doing something
silly like
my $req = APR::Request::Apache2->handle($r);
my $jar = eval {$req->jar} || $...@->jar; # best effort
