Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Preliminary work to allow server to support multiple protocol versions #2017

Closed
NTaylorMullen opened this Issue · 3 comments

3 participants

@NTaylorMullen
Collaborator

Essentially new clients will now pass their expected protocol version via the Query String to the server. If the server does not get a version number it will default to 1.2. Otherwise it will return 1.3. This way the client will be able to determine if it supports a valid protocol version.

@NTaylorMullen NTaylorMullen referenced this issue from a commit
@NTaylorMullen NTaylorMullen Finished server side changes for protocol resolution
- Supports ranges for server protocols
- Also allows replacement of protocol resolver

#2017
72cea88
@NTaylorMullen NTaylorMullen referenced this issue from a commit
@NTaylorMullen NTaylorMullen Updated protocol in JS client
- Also added the feature to pass the clientProtocol in the negotiation request

#2017
6484975
@NTaylorMullen NTaylorMullen referenced this issue from a commit
@NTaylorMullen NTaylorMullen Updated protocol in C# client
- Also added the feature to pass the clientProtocol in the negotiation request

#2017
c8c8a93
@NTaylorMullen NTaylorMullen referenced this issue from a commit
@NTaylorMullen NTaylorMullen Added tests to verify protocol handling on the server
- Includes JS, C# Client, and Server
- Had to add a little bit of extensibility to the test utilities for JS to allow overriding of the WrapConnectionStart functionality

#2017
6212aa9
@NTaylorMullen NTaylorMullen referenced this issue from a commit
@NTaylorMullen NTaylorMullen Finished server side changes for protocol resolution
- Supports ranges for server protocols
- Also allows replacement of protocol resolver

#2017
cf3fa81
@NTaylorMullen NTaylorMullen referenced this issue from a commit
@NTaylorMullen NTaylorMullen Updated protocol in JS client
- Also added the feature to pass the clientProtocol in the negotiation request

#2017
25efb22
@NTaylorMullen NTaylorMullen referenced this issue from a commit
@NTaylorMullen NTaylorMullen Updated protocol in C# client
- Also added the feature to pass the clientProtocol in the negotiation request

#2017
8a150ca
@NTaylorMullen NTaylorMullen referenced this issue from a commit
@NTaylorMullen NTaylorMullen Added tests to verify protocol handling on the server
- Includes JS, C# Client, and Server
- Had to add a little bit of extensibility to the test utilities for JS to allow overriding of the WrapConnectionStart functionality

#2017
56a5e4e
@NTaylorMullen NTaylorMullen referenced this issue from a commit
@NTaylorMullen NTaylorMullen Finished server side changes for protocol resolution
- Supports ranges for server protocols
- Also allows replacement of protocol resolver

#2017
d1f4e4b
@NTaylorMullen NTaylorMullen referenced this issue from a commit
@NTaylorMullen NTaylorMullen Updated protocol in JS client
- Also added the feature to pass the clientProtocol in the negotiation request

#2017
2713fcc
@NTaylorMullen NTaylorMullen referenced this issue from a commit
@NTaylorMullen NTaylorMullen Updated protocol in C# client
- Also added the feature to pass the clientProtocol in the negotiation request

#2017
1b622a7
@NTaylorMullen NTaylorMullen referenced this issue from a commit
@NTaylorMullen NTaylorMullen Added tests to verify protocol handling on the server
- Includes JS, C# Client, and Server
- Had to add a little bit of extensibility to the test utilities for JS to allow overriding of the WrapConnectionStart functionality

#2017
56bf068
@NTaylorMullen NTaylorMullen referenced this issue from a commit
@NTaylorMullen NTaylorMullen Finished server side changes for protocol resolution
- Supports ranges for server protocols
- Also allows replacement of protocol resolver

#2017
fa2a5ad
@NTaylorMullen NTaylorMullen referenced this issue from a commit
@NTaylorMullen NTaylorMullen Updated protocol in C# client
- Also added the feature to pass the clientProtocol in the negotiation request

#2017
994210b
@NTaylorMullen NTaylorMullen referenced this issue from a commit
@NTaylorMullen NTaylorMullen Added tests to verify protocol handling on the server
- Includes JS, C# Client, and Server
- Had to add a little bit of extensibility to the test utilities for JS to allow overriding of the WrapConnectionStart functionality

#2017
b233f1b
@davidfowl
Owner

@NTaylorMullen isn't this done?

@Xiaohongt Xiaohongt was assigned
@NTaylorMullen
Collaborator

Just marked it correctly

@Xiaohongt
Collaborator

verified without querystring and with querystring for different values

@Xiaohongt Xiaohongt closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.