88 2002-11-26 17:13:58 +0000 URI not escaped properly when POST -> GET redirecting 2002-11-26 22:22:25 +0000 1 1 1 Unclassified Validator check 0.6.0 Other other RESOLVED FIXED http://lists.w3.org/Archives/Public/www-validator/2002Nov/0226.html P1 major --- 1 ville.skytta link oldest_to_newest 192 0 ville.skytta 2002-11-26 17:13:58 +0000 Brian J. Saville <bsaville@espeedient.com> in <http://lists.w3.org/Archives/Public/www-validator/2002Nov/0226.html>: If you submit a URL in the Address input box that has multiple query string parameters, the address is not properly parsed. Consider the following URL: http://www.somedomain.com?parameterA=1&parameterB=2 You would expect that the validator would request the URL as it appears above from the specified web server. Instead it requests this: http://www.somedomain.com?parameterA=1 The problem lies in that the ampersand is not be properly encoded. This can be seen by looking at the GET request that is created after submitting the form with the above address to the validator service. The GET looks like: http://validator.w3.org/check?uri=http://www.somedomain.com?parameterA=1 &parameterB=2 In this case, the validator ignores parameter2 thinking that its uri parameter ends at A=1, when really parameter2 should be included as part of the uri parameter and passed on to the host web server. The correct GET should look like this: http://validator.w3.org/check?uri=http://www.somedomain.com?parameterA=1 %26parameterB=2 Currently this can be corrected by hand by changing any ampersand to %26 either in the Address input box on the form or in the GET request for the validator in the address bar. 193 1 ville.skytta 2002-11-26 17:22:25 +0000 Fixed in CVS (HEAD and 0_6_0-branch). Ouch.