- From: Christophe Strobbe <christophe.strobbe@esat.kuleuven.be>
- Date: Fri, 20 Jan 2006 16:06:35 +0100
- To: <w3c-wai-gl@w3.org>
At 19:36 12/01/2006, Michael Cooper wrote: <blockquote> (...) 3) I think I understand what is meant by the technique about server-side redirect. (...) However, the <meta> element is defined in the HTML spec <http://www.w3.org/TR/html401/struct/global.html#edef-META> to provide a "virtual" HTTP header. The "header" that the HTML technique to create refreshing pages uses is called the "Refresh" header, but unfortunately I just discovered that this header is not defined in the HTTP specification <ftp://ftp.isi.edu/in-notes/rfc2616.txt> and as far as I can tell, never was. Nevertheless, I tried putting that HTTP header into a Web server on my local machine, and sure enough, recent versions of Firefox and IE both respected the header and refreshed the page just as if I had defined it in HTML with a <meta> element. Given that this is not defined in the spec, I have no idea if it's a common enough situation for us to write techniques against. But since the browsers support it, I have to imagine the developers anticipated it being used. So possibly we'd want to create "HTTP" techniques about this for the guide doc. </blockquote> Based on Michael's message, I've added the "Failure due to using server-side techniques to automatically redirect pages after a timeout" (with examples for Java Servlets and ASP): http://trace.wisc.edu/wcag_wiki/index.php?title=Failure_due_to_using_server-side_techniques_to_automatically_redirect_pages_after_a_timeout. We may decide to link to it from another success criterion later, but at least it is documented now. Regards, Christophe Strobbe -- Christophe Strobbe K.U.Leuven - Departement of Electrical Engineering - Research Group on Document Architectures Kasteelpark Arenberg 10 - 3001 Leuven-Heverlee - BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
Received on Friday, 20 January 2006 15:06:45 UTC