-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update websockets-next-reference.adoc with Tenants #43144
Conversation
🙈 The PR is closed and the preview is expired. |
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, looks mostly good. Please look at the various suggestions from @mkouba and myself.
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Can you squash your commits into a single one?
@cescoffier |
No worries, I will do that. |
This comment has been minimized.
This comment has been minimized.
Describe how users can access headers in websockets-next and use it in CustomTenantResolver with normal Rest-Calls.
@Paul6552 I just did it - waiting for CI and merging! Thanks for your contribution! |
Status for workflow
|
Merged! Thanks @Paul6552 ! |
Describe how users can access headers in websockets-next and use it in CustomTenantResolver with normal Rest-Calls.