W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2019

Re: The Refresh header is still with us

From: Soni L. <fakedme+http@gmail.com>
Date: Tue, 12 Mar 2019 06:22:59 -0300
To: Daniel Stenberg <daniel@haxx.se>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <01e7f278-feae-3edc-ec53-4b136895308b@gmail.com>

On 2019-03-12 6:19 a.m., Daniel Stenberg wrote:
> On Mon, 11 Mar 2019, Soni L. wrote:
>> I do use Refresh and (deeply-nested) iframes for JS-less webapps. Not 
>> sure what the alternative is here, if any. But they're not redirects.
> So what exactly do you expect this header to do? Refresh the entire 
> page even when just a sub resource response gets it? Is what what it 
> happens? Is that working cross-browser?
> And why use a HTTP header for this, can't you just use a meta tag 
> since you are doing a web page after all? It seems like an odd layer 
> mix to me.
I expect it to refresh a single empty iframe. Once it's no longer empty 
it stops refreshing.

It would be nicer if I could embed HTML snippets into pages, instead of 
full documents, and still get Refresh capabilities. But anyway.

Oh, I also use Refresh for the odd RSS/Atom feed. Not sure if any feed 
readers actually care about rate-limiting themselves following the 
server's lead tho.
Received on Tuesday, 12 March 2019 09:23:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 12 March 2019 09:23:25 UTC