Subject: [http-extensions] Documenting Refresh: HTTP header (#138)

From: HTTP issue updates <[email-masked]>
Date: Thu, 28 Jan 2016 16:25:17 -0800

Maybe @reschke 

In [RFC7538](http://tools.ietf.org/html/rfc7538#section-4) there is a mention of `meta refresh` in HTML. I have seen instances online of a `Refresh` HTTP header. I haven't found any documentation about it in the past (or maybe I missed the appropriate RFC). I [met the header again yesterday](https://bugzilla.mozilla.org/show_bug.cgi?id=668275#c52) in an instance of gmail Web site.

When requesting
`→ http --print hH https://mail.google.com/ 'User-Agent:Mozilla/5.0 (Android 4.4.4; Mobile; rv:44.0) Gecko/44.0 Firefox/44.0' 'Accept-Language:en-US,en;q=0.5'`

```http
HTTP/1.1 200 OK
Alt-Svc: quic=":443"; ma=604800; v="30,29,28,27,26,25"
Alternate-Protocol: 443:quic,p=1
Cache-Control: private, max-age=604800
Content-Length: 306
Content-Type: application/xhtml+xml; charset=ISO-8859-1
Date: Thu, 28 Jan 2016 00:57:39 GMT
Expires: Thu, 28 Jan 2016 00:57:39 GMT
Refresh: 0;URL=https://mail.google.com/mail/
Server: GSE
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
```

You might not be able to reproduce gmail has tons of versions depending on the location, devices, headers, etc.

I have started to [test a bit and write about it last year](http://www.otsukare.info/2015/03/26/refresh-http-header). It seems implemented uniformly, but that would require a bit more test. 

What would be the best course of actions for documenting it? Maybe I can give it a shot. 

---
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/issues/138