httpd-apreq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Schaefer <joe_schae...@yahoo.com>
Subject Re: Cookie parsing errors: conflicting information, expected token not present
Date Mon, 16 Feb 2009 09:35:51 GMT
----- Original Message ----

> From: Clinton Gormley <clint@traveljury.com>
> To: apreq-dev@httpd.apache.org
> Sent: Saturday, February 14, 2009 8:21:51 AM
> Subject: Cookie parsing errors: conflicting information, expected token not present

[...]

> I realise that the cookies themselves may not be compliant, either
> because of bad JS or buggy clients, but CGI.pm manages to parse all of
> the examples below, in the same way that browsers try to cope with dodgy
> HTML. It'd be nice if libapreq were a bit more DWIM.

If you think CGI::Cookie (which is what CGI.pm uses) parses these cookies
correctly, you really haven't looked carefully enough.  The only thing
CGI::Cookie does differently from libapreq2 is that it doesn't throw errors
on stuff it doesn't understand.  Whether that's a bug or a feature is
more a matter of taste than anything else.


      

Mime
View raw message