[chuuminggg]

For a HEAD request, the curl request snippet uses -X HEAD:

$ curl 'http://localhost:8080/items' -i -X HEAD

-X only changes the method name in the request. It doesn't change how curl handles the response, so curl still waits for the number of bytes in the Content-Length header. A response to a HEAD request has no body, so the documented command hangs until it times out. curl's documentation for -X says the same: "if you want to make a proper HEAD request, using -X HEAD does not suffice. You need to use the --head option." (-I is the short form of --head.)

I checked this with curl 8.16.0 against a local server that answers HEAD with Content-Length: 13 and no body:

Command	Result
curl '…/foo' -i -u 'user:secret' -X HEAD -H 'Accept: application/json' --max-time 5	Headers are printed, then curl: (28) Operation timed out after 5002 milliseconds with 0 out of 13 bytes received
curl '…/foo' -I -u 'user:secret' -H 'Accept: application/json' --max-time 5	Finishes in 0.1 s with exit code 0

The server received the same request from both commands: method HEAD, the Authorization header, and the Accept header.

This PR makes the snippet use -I instead of -i -X HEAD for a HEAD request. -I also includes the response headers in the output, so it replaces -i as well. The snippets for other methods are unchanged. The HTTPie snippet doesn't need a change, as http HEAD … already makes a proper HEAD request.

[wilkinsona]

Thanks again, @chuuminggg.