Skip to content

Add client.protocol override option for client#218

Merged
shellscape merged 4 commits intoshellscape:masterfrom
pappasam:customize-client-protocol-scheme
Mar 13, 2021
Merged

Add client.protocol override option for client#218
shellscape merged 4 commits intoshellscape:masterfrom
pappasam:customize-client-protocol-scheme

Conversation

@pappasam
Copy link
Contributor

@pappasam pappasam commented Mar 5, 2021

This PR contains:

  • bugfix
  • feature
  • refactor
  • tests
  • documentation
  • metadata

Breaking Changes?

  • yes
  • no

If yes, please describe the breakage.

Please Describe Your Changes

Small, yet important (for me, at least :p) update: enables users of reverse proxies to specify a different protocol scheme for client requests (typically wss from the browser) from the protocol scheme served by the server (typically ws).

Provides the final, necessary tool to resolve: #172.

pappasam added 3 commits March 5, 2021 15:06
Enables users of reverse proxies to specify a different protocol scheme
for client requests (typically `wss` from the browser) from the protocol
scheme served by the server (typically `ws`).
@shellscape
Copy link
Owner

Looks good 👍 Just a small variable name reversion I'd appreciate.

Co-authored-by: Andrew Powell <shellscape@users.noreply.github.com>
@pappasam
Copy link
Contributor Author

@shellscape done!

@shellscape shellscape merged commit c747018 into shellscape:master Mar 13, 2021
@shellscape
Copy link
Owner

thanks!

@pappasam
Copy link
Contributor Author

@shellscape any idea when we can expect an npm release with this new feature? I'm itching to get it into our local dev environment!

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.

Example minimal config for https

2 participants