Skip to content
This repository has been archived by the owner on Oct 18, 2018. It is now read-only.

WebSocket Middleware considers Connection: keep-alive, upgrade as non-WebSocket request #123

Closed
analogrelay opened this issue Oct 17, 2016 · 3 comments

Comments

@analogrelay
Copy link
Contributor

Firefox sends it's WebSocket upgrade request with a Connection header value of keep-alive, Upgrade. But we check for the header to exactly equal Upgrade.

if (string.Equals(Constants.Headers.ConnectionUpgrade, pair.Value, StringComparison.OrdinalIgnoreCase))

Similar to aspnet/KestrelHttpServer#1170

@analogrelay analogrelay self-assigned this Oct 17, 2016
@analogrelay
Copy link
Contributor Author

Ping @muratg for Triage. I assume 1.1.0 RTM for now.

@muratg muratg added this to the 1.1.0 milestone Oct 17, 2016
@Tratcher
Copy link
Member

This implementation is actually OK. See

foreach (var value in _context.Request.Headers.GetCommaSeparatedValues(headerName))
where it splits the header values.

This is only blocked by the kestrel issue. It works with WebListener.

@muratg
Copy link

muratg commented Nov 2, 2016

Closing based on @Tratcher's input.

@muratg muratg closed this as completed Nov 2, 2016
@muratg muratg removed this from the 1.0.0 milestone Nov 2, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants