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 host restriction #492

Closed
mnot opened this issue Jun 4, 2014 · 7 comments
Closed

Alt-Svc header host restriction #492

mnot opened this issue Jun 4, 2014 · 7 comments

Comments

@mnot
Copy link
Member

mnot commented Jun 4, 2014

When we were originally working on Alt-Svc, Patrick and I put a restriction on the Alt-Svc header field so that it couldn’t redirect clients to a different host.

Since then, several people have pointed out that the requirement to have strong server authentication, as well as cache flushing, seems to contain the risk associated with doing this, and that the facility could be quite useful.

So, I’m suggesting we (re-) add the capability to the header.

@mnot
Copy link
Member Author

mnot commented Jun 5, 2014

Discussed in NYC; do it.

@reschke
Copy link
Contributor

reschke commented Jun 9, 2014

Two questions:

  1. the text around the ALTSVC frame currently talks about IDNA; I assume the same considerations would apply for the header field once we include the host, right?

  2. if we change the value from port to host:port we'll have to allow quoted-string syntax as well (because of the ":"), right?

@martinthomson
Copy link
Collaborator

Yes, IDNA restrictions apply equally (to bother or neither). The colon sucks, if you want a consistent grammar. (I suppose Host is an exception in that regard.)

@reschke
Copy link
Contributor

reschke commented Jun 10, 2014

On 2014-06-10 01:32, Martin Thomson wrote:

Yes, IDNA restrictions apply equally (to bother or neither). The colon
sucks, if you want a consistent grammar. (I suppose Host is an exception
in that regard.)

We already require understanding of quoted-string when processing the
parameters, so I'll stick to the colon and make the value
token/quoted-string.

Best regards, Julian

@reschke reschke self-assigned this Jun 12, 2014
@enygren
Copy link

enygren commented Jun 12, 2014

Do we need to clarify whether IP addresses (IPv4 and/or IPv6) are or are not allowed?
If so, for the IPv6 case are the square brackets required and do the colons need to be escaped?

@reschke
Copy link
Contributor

reschke commented Jun 12, 2014

The intent is to allow exactly what's allowed in an HTTP Host header field, which includes IP addresses.

See http://greenbytes.de/tech/webdav/rfc3986.html#host

So yes, IPv6 addresses would require square brackets. And no, colons would not need any additional escaping.

reschke added a commit that referenced this issue Jun 12, 2014
@reschke
Copy link
Contributor

reschke commented Jun 12, 2014

Still need to explain what checks need to be done when switching hosts; see http://lists.w3.org/Archives/Public/ietf-http-wg/2014AprJun/1232.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants