-
Notifications
You must be signed in to change notification settings - Fork 90
fix: propagate WS subprotocols from sec-websocket-protocol header for v4 APIs #13932
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
fix: propagate WS subprotocols from sec-websocket-protocol header for v4 APIs #13932
Conversation
Summary of ChangesHello @vikrantgravitee, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses an issue where WebSocket subprotocols were not being correctly propagated in V4 APIs, leading to inconsistent behavior compared to V2 APIs. It introduces changes to parse the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
This pull request introduces two main changes: propagating WebSocket subprotocols from the sec-websocket-protocol header and fixing the endpoint URI in logs for v4 WebSocket APIs. The implementation for parsing subprotocols is robust, handling multiple headers and comma-separated values correctly. The endpoint URI construction also appears correct. My main feedback is a suggestion to improve encapsulation by using protected getters instead of changing field visibility from private to protected, which is a better long-term design choice. Overall, the changes are well-implemented and address the described issues.
Issue
https://gravitee.atlassian.net/browse/APIM-11807
Description
Additional context