Added StickySessions feature for process dipatching (tjanczuk/iisnode/pull/384) #31
Conversation
This file contains hidden or 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
Setting nodeProcessStickySessions to true will set a cookie on a client's first request, carrying a hint for the target node.exe process. Each subsequent request will then be routed to the process mentioned in the cookie.
Cookie parsing routine did not work in case of missing ';'
|
@rramachand21 Any chance we can get this merged? Azure already provides stickiness at the server level so this would allow us to upgrade our applications to some of the larger instances. |
Closed
|
This is included in https://github.com/Azure/iisnode/releases/tag/v0.2.25 |
|
That's awesome! We're super eager to try this out as soon as it's available in App Service. |
|
Please note - do not use v0.2.24. Use v0.2.25. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Reopen this pull request in this more active fork of iisnode.
Plus a small fix based on tjanczuk#384 (comment)