ISSUE-156: Support HTTP Refresh header?
Support HTTP Refresh header?
- State:
- CLOSED
- Product:
- mobileOK Basic tests
- Raised by:
- Sean Owen
- Opened on:
- 2006-10-19
- Description:
- During the 10/19 call, Jo proposed revisiting our decision on the \"Refresh\"
header, and I tend to agree. We resolved to not write tests that refer to the
Refresh header since HTTP does not define such a header. But our tests refer to
<meta> tags with http-equiv=\"Refresh\", which we might exclude for exactly the
same reason. We don\'t of course since it\'s widely used. Jo further adds that
some browsers respond to Refresh as an HTTP header. I personally see no harm in
mentioning its header form in the tests. Dom had some objections to this, so I\'m
re-raising as an issue. - Related Actions Items:
- No related actions
- Related emails:
- Re: Minutes Call Oct 26 (from dom@w3.org on 2006-10-27)
- Re: ISSUE-156: Support HTTP \\\'Refresh\\\' header? (from chaals@opera.com on 2006-10-26)
- Re: ISSUE-156: Support HTTP \\\'Refresh\\\' header? (from dom@w3.org on 2006-10-25)
- RE: ISSUE-156: Support HTTP \\\'Refresh\\\' header? (from jo@linguafranca.org on 2006-10-25)
- ISSUE-156: Support HTTP \\\'Refresh\\\' header? (from dean+cgi@w3.org on 2006-10-19)
- RE: ISSUE-156: Support HTTP \\\'Refresh\\\' header? (from k.scheppe@t-online.net on 2006-10-19)
Related notes:
(Fixed the title, for posterity, after being unable to find this for ages. I
think the quote characters threw off trackbot and truncated the title)
Display change log
