Add websocket/http request to client object during connection #322
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This would need docs and a test, otherwise I’m good to add this. |
|
Thanks for the quick attention! I added a websocket-stream based server + client test modeled after similar tests in I also added brief notes to README.md on the |
gnought
reviewed
Sep 13, 2019
|
LGTM |
|
please make a release with this feature |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Servers based on websocket-stream require access to the original HTTP request headers in order to access the
X-Forwarded-Foror any other interesting HTTP header.I've done the minimal possible work to attach the original HTTP request to aedes' Client object so that it's available later on.