-
Notifications
You must be signed in to change notification settings - Fork 204
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
hq Alt-Svc quic parameter and structured headers #1093
Comments
Technically, it's a non-issue, since Alt-Svc isn't defined to be a structured header. However, the goal is to track that draft as closely as reasonable, since it also represents a best practice. I'll take a look and see if there's a simple change that would bring us closer, but I also don't want change for change's sake. |
Seems like the simplest choice would be a comma-delimited quoted string, i.e.
That certainly makes it shorter and matches the guidance, at the price of updating everyone's parser again. What do folks think? |
I have no strong stake. Good point about structured header / best common practice. |
So, oddly enough GQUIC has already started supporting the newly proposed IETF Alt-Svc, but if we're going to change it, sooner would be better. And if you change it again after this time, we'll probably start getting grumpy :) But shorter and following best practices seem like general goodness. |
+1 on sooner the better. |
+1 -- Let's do this, and ASAP.
…On Fri, Feb 2, 2018 at 3:35 PM, Subodh Iyengar ***@***.***> wrote:
+1 on sooner the better.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1093 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKjg1GBKYo_NbQhEGSC4sTsQUW7smFM6ks5tQ5u8gaJpZM4R3PmO>
.
|
I think the current syntax of the "quic" parameter for hq Alt-Svc is, after recent changes, incompatible with structured headers. For reference, httpwg/http-extensions#281 provides history of the issue. This ticket highlights that HTTP/QUIC is now incompatible.
Please close this out if a non-issue.
The text was updated successfully, but these errors were encountered: