-D, --dump-header <file>
Write the protocol headers to the specified file.
This option is handy to use when you want to store the headers
that a HTTP site sends to you. Cookies from the headers could
then be read in a second curl invocation by using the -b,
--cookie option! The -c, --cookie-jar option is however a better
way to store cookies.
e
-S, --show-error
When used with -s, --silent, it makes curl show an error message if it fails.
e
-L/--location
(HTTP/HTTPS) If the server reports that the requested page has moved to a different location (indicated with a Location: header and a 3XX response
code), this option will make curl redo the request on the new place. If used together with -i/--include or -I/--head, headers from all requested
pages will be shown. When authentication is used, curl only sends its credentials to the initial host. If a redirect takes curl to a different
host, it won’t be able to intercept the user+password. See also --location-trusted on how to change this. You can limit the amount of redirects to
follow by using the --max-redirs option.
When curl follows a redirect and the request is not a plain GET (for example POST or PUT), it will do the following request with a GET if the HTTP
response was 301, 302, or 303. If the response code was any other 3xx code, curl will re-send the following request using the same unmodified
method.
da página do manual. tão
curl -sSL -D - www.acooke.org -o /dev/null
segue redirecionamentos, despeja os cabeçalhos para stdout e envia os dados para / dev / null (isso é um GET, não um POST, mas você pode fazer a mesma coisa com um POST - basta adicionar qualquer opção que você já esteja usando para os dados do POST)
observe o -
depois do -D
que indica que o "arquivo" de saída é stdout.
curl -s -D - http://yahoo.com -o nul