On Wed, Nov 18, 2009 at 12:11 PM, Jonathan Vanasco <[email protected]>wrote:

> On Nov 16, 2:50 pm, Ben Bangert <[email protected]> wrote:
>
> > - Fixed bug in Python stdlib regarding handling of 'bad' cookies. Ie, if
> Python is parsing 4 cookies, and the first one is 'invalid', Python *stops
> parsing* the rest! This is bad as several webapp systems use the character
> Python doesn't like, so having it on the same domain as a Python app (not
> werkzeug) means cookies just disappear since Python stops parsing them.
>
> the 'bad cookie' thing would be great to see happen sooner-than-
> later.  a few years ago, wordpress created malformed cookies ( they
> didn't conform to the RFC and either used restricted chars , or didn't
> quote or something, i can't remember ).  a project that i had ran
> wordpress for the blog/news , and mod-perl for an application.  the
> second libapreq ( the  cooking parsing apache module ) encountered a
> malformed cookie... segfault.  its a rare thing to have, but
> incredibly frustrating to deal with if it ever happens.
>

If someone wants to work on this, WebOb is in bitbucket now, so you can
clone and patch and do a pull request: http://bitbucket.org/ianb/webob


-- 
Ian Bicking  |  http://blog.ianbicking.org  |
http://topplabs.org/civichacker

--

You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected].
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=.


Reply via email to