This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
When given "/check?uri=referer;foo=bar", the extra CGI parameters are not preserved in the resulting redirect.
May be, one wants have the "/check/referer?foo=bar" also preserve any additional parameters. Because this was the first thing I tried and I guess, most people would try this first. It's just because the validator page recommends that "/check/referer" URL and most unexperienced people like me don't know about that "/check?uri=referer"-Feature.
I found some links on the validation page with the same problem. When I open http://validator.w3.org/check?uri=http%3A%2F%2Frw7.de%2Fralf%2Ffavicon.ico;No200=1 then the link named "verbose results" points to http://validator.w3.org/check?uri=http%3A%2F%2Frw7.de%2Fralf%2Ffavicon.ico;verbose=1 thus drops the No200=1. The same with the "If you would like to create a link to this page"-link.
The issue in Comment #2 is similar but different from Bug #278; in the latter we lose all CGI params during the redirect, in the former we simply fail to propogate the No200 param. They are similar enough however that I'll probably fix them both at the same time. Additional CGI parameters on the /check/referer URL (cf. Comment #1) are not supported and I feel no strong need to make them so. What might make sense is to begin emitting the /check?uri=referer style of URLs in Validation results.
Fixed. The updated code will be in the next beta release. Please verify that all your test cases work at that time and reopen this bug if I missed something.
Thank you very much. For anyone, who wants to make a quick check, when the code is online, try http://rw7.de/ralf/favicon.ico and click on the validator icon at the right.