3 ms·
It isn't a solved problem because standards are evolving. The most noticeable ones are related to encryption, but there are also HTTP2, WebSockets, QUIC and oth
by reisse 4y ago
It isn't a solved problem because standards are evolving. The most noticeable ones are related to encryption, but there are also HTTP2, WebSockets, QUIC and other protocols you need to speak on the web.
- mgaunard 4y agoWebSocket isn't supported by curl. HTTP 2/3 are mostly bad ideas (slightly less bad in the case of 3, but still overkill) pushed by Google to optimize an edge case no one but web browsers care about. curl doesn't fully support HTTP 3 regardless.
- reisse 4y ago> WebSocket isn't supported by curl. Not yet in command-line, but libcurl has support. Besides, that's the task to work on full-time :) https://curl.se/docs/websocket.html https://curl.se/docs/websocket.html > to optimize an edge case no one but web browsers care about. I'd argue there are no reasonable use-cases for HTTP except web browsers.