![\"\"\/](\"https:\/\/imgs.xkcd.com\/comics\/duty_calls.png\")
<\/a><\/figure>\n<\/div>\n\n\nStarting with curl<\/a> 7.45.0 (due to ship October 7th 2015), the tool will help users to understand that their use of the Example:<\/p>\n\n\n\n The option dash capital i<\/a> means asking curl to issue a HEAD request. Adding It’ll also inform the user similarly if you do $ curl -v -d hello -XPOST http:\/\/example.com\nNote: Unnecessary use of curl will still continue to work exactly like before though, these are only informational texts that won’t alter any behaviors. Again, it only says this if verbose mode is enabled.<\/p>\n\n\n\n When doing HTTP with curl, the -X option changes the actual method string in the HTTP request. That’s all it does. It does not change behavior accordingly<\/strong>. It’s the perfect option when you want to send a DELETE<\/a> method or TRACE<\/a> or similar that curl has no native support for and you want to send easily. You can use it to make curl send a GET with a request-body or you can use it to have the I know several users out there will disagree with this. That’s also why this is only shown in verbose mode and it only says “Note:” about it. For now.<\/p>\n\n\n\n There are a few problems with the superfluous uses of -X in curl:<\/p>\n\n\n\n One of most obvious problems is that if you also tell curl to follow HTTP redirects (using But even without following redirects, just throwing in an extra The perhaps biggest mistake you can do with … which will have curl act as if it sends a GET<\/a> but it sends a HEAD. A response to a HEAD<\/a> never has a body, although it sends the size of the body exactly like a GET response which thus mostly will lead to curl to sit there waiting for the response body to arrive when it simply won’t and it’ll hang.<\/p>\n\n\n\n Starting with this change, this is the warning it’ll show for the above command line:<\/p>\n\n\n\n Warning: Setting custom HTTP method to HEAD may not work the way you want.<\/p>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":" I’ve grown a bit tired of the web filling up with curl command line examples showing use of superfluous -X’s. I’m putting code where my mouth is. Starting with curl 7.45.0 (due to ship October 7th 2015), the tool will help users to understand that their use of the -X (or –request) is very often … Continue reading Unnecessary use of curl -X<\/span> -X<\/code><\/a> (or --request<\/code><\/a>) is very often unnecessary or even downright wrong. If you specify the same method with -X<\/code> that will be used anyway, and you have verbose mode<\/a> enabled, curl will inform you about it and gently push you to stop doing it.<\/p>\n\n\n\n$ curl -I -XHEAD http:\/\/example.com --verbose<\/pre>\n\n\n\n
-X HEAD<\/code> to that command line asks for it again<\/em>. This option sequence will now make curl say:<\/p>\n\n\n\nNote: Unnecessary use of -X or --request, HEAD is already inferred.<\/pre>\n\n\n\n
-XGET<\/code> on a normal fetch or -XPOST<\/code> when using one of the -d options. Like this:<\/p>\n\n\n\n-X<\/code> or --request<\/code>, POST is already inferred.<\/p><\/pre>\n\n\n\nWhat -X does<\/h2>\n\n\n\n
-d<\/code> option work even when you want to send a PUT. All good uses.<\/p>\n\n\n\nWhy superfluous -X usage is bad<\/h2>\n\n\n\n
-L<\/code> or --location<\/code><\/a>), the -X<\/code> option will also be used on the redirected-to requests which may not at all be what the server asks for and the user expected. Dropping the -X will make curl adhere to what the server asks for. And if you want to alter what method to use in a redirect, curl already have dedicated options for that named --post301<\/code><\/a>, --post302<\/code><\/a> and --post303<\/code><\/a>!<\/p>\n\n\n\n-X<\/code> “to clarify” leads users into believing that -X has a function to serve there when it doesn’t. It leads the user to use that -X<\/code> in his or her’s next command line too, which then may<\/em> use redirects or something else that makes it unsuitable.<\/p>\n\n\n\n-X<\/code>, and one that now actually leads to curl showing a “warning”, is if you’d use -XHEAD<\/code> on an ordinary command line (that isn’t using -I<\/code><\/a>). Like this (I’ll display it crossed over to make it abundantly clear that this is a bad<\/strong> command line):<\/p>\n\n\n\n$ curl -XHEAD http:\/\/example.com\/<\/s><\/pre>\n\n\n\n\n