Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple Refresh headers #2900

Open
annevk opened this issue Aug 9, 2017 · 3 comments
Open

Multiple Refresh headers #2900

annevk opened this issue Aug 9, 2017 · 3 comments

Comments

@annevk
Copy link
Member

@annevk annevk commented Aug 9, 2017

When you have

Refresh: 0
Refresh: hi

should that be treated as 0,hi or an error? Most browsers treat it as the former, but at least for Firefox that's inconsistent with Location.

Filed https://bugzilla.mozilla.org/show_bug.cgi?id=1387032 to figure out Mozilla's position.

@gibson042
Copy link
Contributor

@gibson042 gibson042 commented Aug 9, 2017

Possibly relevant spec references:
HTTP/1.1 prohibits senders from generating headers with duplicate names "unless either the entire field value for that header field is defined as a comma-separated list [i.e., #(values)] or the header field is a well-known exception [i.e., Set-Cookie]", but provides no guidance on what recipients of such malformed messages should do.
HTTP/2 allows but does not require servers to generate a response, but requires clients to reject malformed responses (which include those with header errors).

Since Refresh doesn't make sense as a comma-separated list, treating extra assignments as errors seems logical.

Loading

@mcmanus
Copy link

@mcmanus mcmanus commented Aug 18, 2017

So I can't find a definiton of refresh (though the dom code supports it).. I suggest you define it, and then we can treat it like location

Loading

@annevk
Copy link
Member Author

@annevk annevk commented Aug 21, 2017

Step 9 of https://html.spec.whatwg.org/#initialise-the-document-object defines it, but currently multiple headers is an open issue.

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
@mcmanus @gibson042 @annevk and others