This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
A lot of sites are using browser check functionality before letting a browser enter the requested page. This is also true for the validator client. Please follow redirecte(status 302) to receive the wanted page to validate!
Do you have a sample page for which the Validator does not follow the redirect? It should follow them already, I'd rather suspect that this is a <meta> or script-based redirect. We can't really follow script-based redirection and for <meta> there is some other feature request already.
(In reply to comment #1) > Do you have a sample page for which the Validator does not follow the redirect? > It should follow them already, I'd rather suspect that this is a <meta> or > script-based redirect. We can't really follow script-based redirection and for > <meta> there is some other feature request already. Yes: http://pingo.cv.ihk.dk:8080/NetBanken/pages/home.jsf
(In reply to comment #2) > > Do you have a sample page for which the Validator does not follow the > > redirect? > Yes: http://pingo.cv.ihk.dk:8080/NetBanken/pages/home.jsf I don't see why you complain that the validator does not follow redirect. It does, but fails to follow it to an acceptable target, and detects a redirect loop. I haven't had time to look into it thoroughly, but I suspect your redirection code is broken for user agents that do not accept cookies.
(Follow-up to comment #3) > I don't see why you complain that the validator does not follow redirect. It does, but fails to follow it to > an acceptable target, and detects a redirect loop. I haven't had time to look into it thoroughly, but I > suspect your redirection code is broken for user agents that do not accept cookies. Indeed. Testing with my browser and refusing the cookie got me in a redirection loop. Your redirection code is broken. Closing INVALID.