-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 André,
On 12/17/11 9:37 AM, André Warnier wrote: > I do not see anything in the above that submits anything with an > "umlaut". The form could have additional <inputs> that were not included in the OP. > This is a "GET" request, so anything submitted would have to be in > the URL, as a query-string. Most web browsers are smart enough to merge the query string from the <form action> and form the <inputs> though I found dealt with an issue recently where that didn't work properly. I can't remember what it was... probably Safari. > I only see "name" here. The quotes appear wrong too. +1 > There is also a double // after 8080, where it should not be. It shouldn't be there, but it also shouldn't be a problem. It's just sloppy. > Are you sure it is not simply the "action" of your <form> which is > wrong ? If the above bug (failure to merge query-string and form <input> parameters) is the problem, then the OP might end up with 'null' being read from the request -- IIRC that was my observation. The solution IMO is to always use POST whenever you are expecting non-US-ASCII in your form inputs. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7vvNUACgkQ9CaO5/Lv0PAl/gCfbFlZ7mulTmeKrEr92WxIMh9+ QGoAoKjNZulYD0kibYrShP85dp2pZsxL =fecP -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
