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

Always Upgrade #29

Closed
martinthomson opened this issue Feb 19, 2013 · 2 comments
Closed

Always Upgrade #29

martinthomson opened this issue Feb 19, 2013 · 2 comments

Comments

@martinthomson
Copy link
Collaborator

We need to resolve whether an Upgrade is always necessary, or whether clients can start the HTTP/2.0 session immediately if they have prior knowledge about server capabilities.

Requiring upgrade might be necessary if the set of intermediaries or servers that are involved are potentially homogenous. For example, a phased upgrade of a load-balanced server farm might result in some servers being HTTP/2.0-capable and others not.

@mnot
Copy link
Member

mnot commented Feb 27, 2013

Based on list discussion, it appears that we will allow connections (HTTP and HTTPS) to go without Upgrade, but with the Magic. We'll need to give some implementation guidance, of course.

@martinthomson
Copy link
Collaborator Author

Sounds like a resolution to me.

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

No branches or pull requests

2 participants