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

Alt-Svc header with 421 status #75

Closed
MikeBishop opened this issue May 28, 2015 · 1 comment

Comments

Projects
None yet
3 participants
@MikeBishop
Copy link
Contributor

commented May 28, 2015

Why does the spec explicitly allow the alternate to simultaneously send you an alternate list (which we trust, because the alternate is authoritative for this origin) and a status code telling us this host is not authoritative for this origin?

It seems like 421 should automatically remove the alternate (as stated) and cause the user agent to fall back to the origin server. While one can also envision a scenario where the server says "I'm not authoritative, but I know who might be....", that way lies loops.

@reschke reschke added the alt-svc label May 30, 2015

@mnot mnot added the design label Jun 8, 2015

@mnot

This comment has been minimized.

Copy link
Member

commented Jul 21, 2015

Discussed in Prague; an alt-svc header in a 421 response MUST be ignored.

@mnot mnot added the editor-ready label Aug 24, 2015

reschke added a commit that referenced this issue Sep 1, 2015

@reschke reschke closed this Sep 1, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.