To follow-up from the previous post being about curl, WebSockets and Nginx, now let’s see how to check HTTP versions supported by an endpoint with curl of course. the command We gonna test by fetching HEAD requests only (not GET) and that’s being done with passing the --head parameter or -I for the short version of it. This approach should be efficient enough since we only need the response headers to determine the HTTP version. ...
We all know we could use curl anytime with HTTP requests but what about WebSockets? I was debugging a WebSocket the other day which was basically a Docker service sitting behind an Nginx reverse proxy so I figured I’d write it down. But, first of all, a bit of basics. http vs websockets HTTP is request and response. Stateless. You ask for something, the server responds, and that’s it. WebSockets are stateful. They create a persistent, two-way connection between your browser and the server on. Think of it like UDP but running on top of TCP and as part of the application layer lol. ...