[go: up one dir, main page]
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.

Sign up for GitHub

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

Jump to bottom

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
Labels
interop Implementations are not interoperable with each other topic: navigation

Comments

@annevk
Copy link
Member
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.
annevk added a commit that referenced this issue Aug 9, 2017
@annevk
Define the HTTP Refresh header
7e9f6b6 
Fixes https://www.w3.org/Bugs/Public/show_bug.cgi?id=28339 and fixes https://www.w3.org/Bugs/Public/show_bug.cgi?id=28563.

Tests: web-platform-tests/wpt#6606.

Follow-up: #2900.
@gibson042
Copy link
Contributor

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.

@annevk annevk mentioned this issue Aug 10, 2017
Merged
@mcmanus
Copy link
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

@annevk
Copy link
Member Author
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.

@annevk annevk mentioned this issue Nov 23, 2018
Open
alice pushed a commit to alice/html that referenced this issue Jan 8, 2019
@annevk
Define the HTTP Refresh header
17fb87d 
Fixes https://www.w3.org/Bugs/Public/show_bug.cgi?id=28339 and fixes https://www.w3.org/Bugs/Public/show_bug.cgi?id=28563.

Tests: web-platform-tests/wpt#6606.

Follow-up: whatwg#2900.
@domenic domenic added the interop Implementations are not interoperable with each other label Aug 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
interop Implementations are not interoperable with each other topic: navigation
Milestone
No milestone
Development

No branches or pull requests
5 participants
@mcmanus @domenic @gibson042 @annevk and others