Skip to content

Conversation

@saurabhraghuvanshii
Copy link
Contributor

Notes for Reviewers

  • The proxy now recognises any request that carries Upgrade: websocket and transparently turns itself into a WebSocket tunnel instead of doing a plain HTTP round-trip.
  • A new helper (proxyWebsocket) upgrades the client connection.
  • Normal HTTP traffic is still handled exactly as before.

This PR fixes #27

Signed commits

  • Yes, I signed my commits.

Signed-off-by: saurabhraghuvanshii <saurabhsraghuvanshi@gmail.com>
@leecalcote
Copy link
Member

@saurabhraghuvanshii, thanks for this. What test cases have you exercised with this change in place?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Error during WebSocket handshake: Unexpected response code: 422

2 participants