-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
Websocket docs miss an example of using wss:// #9936
Comments
WebSocket support is still early and we have not even made any particular changes for the curl command line tool for it. Feel most welcome to help us improve in this area. What "specific syntax with escaping quotes" are you referring to? I don't see why using |
Since websocket is an interactive protocol, I think curl must treat responses like we use telnet.exe to read emails from POP3. You send a email server address, it asks you for login. You send your login, it asks for the password. Then it sends you a list of options like reading/removing emails and etc.
I mean this this case: https://stackoverflow.com/questions/32122586/curl-escape-single-quote |
Sending double and single quotes in command lines can certainly be challenging to quote correctly (especially as *nix shells and Windows will do them differently), but I fail to see how that is particularly related to websocket. |
I don't mean that is specific to websocket, I mean what you just said in your last comment should be mentioned in the docs. Can I donate crypto to you? |
I actually don't think shell-quoting should be mentioned much in the curl docs. That is a shell problem and should be detailed in shell documentation. But sure, a small example somewhere could be worthwhile.
No. (I refuse to get involved with anything "crypto".) |
Daniel, to complete this post. |
Which websockets docs did you read when you missed the |
Hi.
The long-awaited Websocket finally landed in curl trunk on 26 October 2022. But the docs are missing an example of how to make a request to a wss address and get a respond via bash or Windows command line with curl-7.86.0.exe.
Windows requires specific syntax with escaping quotes.
Thank you again for websocket.
The text was updated successfully, but these errors were encountered: