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

Characteristics of pre-Upgrade request #52

Closed
martinthomson opened this issue Mar 18, 2013 · 2 comments
Closed

Characteristics of pre-Upgrade request #52

martinthomson opened this issue Mar 18, 2013 · 2 comments

Comments

@martinthomson
Copy link
Collaborator

@martinthomson martinthomson commented Mar 18, 2013

The following attributes - which are normally attributed to HTTP/2.0 requests - are not available for the pre-Upgrade request in HTTP/1.1. These require defaults:

  • Stream ID (default to 1)
  • Priority (default to 0.5/2^30)

We also need to determine the status of the stream, which probably needs to be half-closed from the server side.

@ghost ghost assigned martinthomson Jun 13, 2013
@mnot
Copy link
Member

@mnot mnot commented Jun 13, 2013

Discussed at SF Interim; Martin to incorporate stream ID 1; priority 0.

@mnot
Copy link
Member

@mnot mnot commented Jun 13, 2013

HTTP/1.1 request must be complete before client starts sending HTTP/2. This will block further requests on the connection until the upgrade is effective.

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

2 participants