This is a suggestion for a slight modification in the
jakarta implementation of
javax.servlet.http.HttpUtils. If this is the wrong
forum for that I apologize.
I'm using tomcat with a client app which has a sloppy
form-urlencode. It will product a POST body like
"a=1&b&c=2" - with no equal sign after the b.
Currently, this causes HttpUtils.parseQueryString to
throw an IllegalArgumentException. While this is
technically correct, it does prevent the use of Tomcat
with that client.
My first choice would be to interpret "a=1&b&c=2" as
meaning that b="". It seems like a fairly unambiguous
interpretation. The attached diff makes that change.
Regards,
Rob Lucier
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
HttpUtils.no_equal_sign_fix.diff
