[pubcookie-dev] cgic version

[Jeffrey Eaton]

How far has the pubcookie cgic library diverged from the boutell.com 
cgic sources?  Would it be worth importing the modifications from the 
master sources, or contributing our changes back to boutell?

I ask only because I recently came across a bug that is fixed in the 
latest boutell sources, but not in pubcookie's copy.  Specifically, we 
have some users with blackberry devices, and a recent update to the web 
browser on the device changed how they interact with pubcookie.  When 
the user submits the login form to the login server, the blackberry 
sends the following header:

Content-type: application/x-www-form-urlencoded; encoding=iso-8859-1

The current pubcookie/cgic code only matches on the string 
'application/x-www-form-urlencoded', so cgic never processes the form 
arguments, so the login server code never gets the username and 
password.  The latest cgic code only matches up to the first semicolon, 
so it would have worked.

In this case, I patched the pubcookie/cgic code to do the right thing, 
but before I check it in to CVS, I wanted to get a feel for what people 
thought about merging the rest of the boutell updates as well.

-jeaton