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

Associating Alt-Svc header with an origin #21

Closed
mnot opened this issue Aug 18, 2014 · 7 comments

Comments

Projects
None yet
3 participants
@mnot
Copy link
Member

commented Aug 18, 2014

I think we need to be REALLY careful about making assertions about an origin in a response, given things like pretty-bad-proxy.

Section 3 says:

Alt-Svc MAY occur in any HTTP response message, regardless of the status code.

That's way too broad. For example, what if it's in response to a CONNECT -- will clients associate it with the origin?

I think the resolution of this will need to reference this:
http://httpwg.github.io/specs/rfc7231.html#identification

@mnot mnot added alt-svc labels Aug 18, 2014

@mnot

This comment has been minimized.

Copy link
Member Author

commented Jan 21, 2015

Discussed in HNL; editorial.

@mnot mnot added editorial and removed design labels Jan 21, 2015

@mnot

This comment has been minimized.

Copy link
Member Author

commented Feb 11, 2015

Suggest:

"Alt-Svc MUST be ignored in messages whose payloads are not the payload is known to be a representation of the resource identified by the effective request URI (see [RFC7231], Section 3.1.4.1)."

@martinthomson

This comment has been minimized.

Copy link
Contributor

commented Feb 11, 2015

Suggestion does not parse.

@mnot

This comment has been minimized.

Copy link
Member Author

commented Feb 11, 2015

2nd try:

"Alt-Svc MUST be ignored in messages whose payloads are not known to be a representation of the resource identified by the effective request URI (see [RFC7231], Section 3.1.4.1)."

@martinthomson

This comment has been minimized.

Copy link
Contributor

commented Feb 12, 2015

Yeah, a little laboured, but fine.

@mnot

This comment has been minimized.

Copy link
Member Author

commented Feb 20, 2015

Thinking about this a bit more, that's probably not a good match; it means that Alt-Svc has to be ignored on most POST responses, which is weird.

Perhaps we just need a caveat;

"Alt-Svc MAY occur in any HTTP response message, regardless of the status code. Note that recipients of Alt-Svc are free to ignore the header field (and indeed are require to in some situations; see [ref to 2.1])."

?

@reschke

This comment has been minimized.

Copy link
Contributor

commented Jul 20, 2015

WFM.

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.