-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
websocket: add option to disable auto-pong reply #16744
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
Conversation
Does anything remain to do, to move this PR forward? |
@viscruocco the PR itself looks fine - now we only need to wait for the feature window to open again to allow new features such as this to get merged (for 8.14.0). The feature window for 8.13.0 closed a few weeks ago. You can prepare for this to make sure the PR speaks of the correct version for this feature. The feature window is planned to open again on April 12. |
08583c0
to
3390d40
Compare
This adds another bitflag on CURLOPT_WS_OPTIONS (CURLWS_NOAUTOPONG) that disables the default and automatic PONG reply in the WebSocket layer. Authored-by: brimonk on github
Co-authored-by: Viktor Szakats <vszakats@users.noreply.github.com>
3390d40
to
0d298e0
Compare
Thanks, both of you! |
This adds another bitflag on CURLOPT_WS_OPTIONS (CURLWS_NOAUTOPONG) that disables the default and automatic PONG reply in the WebSocket layer. Assisted-by: Calvin Ruocco Closes curl#16744
This adds another bitflag on CURLOPT_WS_OPTIONS (CURLWS_NOAUTOPONG) that disables the default and automatic PONG reply in the WebSocket layer. Assisted-by: Calvin Ruocco Closes curl#16744
Rebased #12220 with kind permission of @brimonk.
Additionally added some more documentation and explicitly initialized CURLOPT_WS_OPTIONS values to their defaults.