mirror of
https://github.com/curl/curl.git
synced 2024-12-21 06:50:10 +08:00
2bc1d775f5
- they are mostly pointless in all major jurisdictions - many big corporations and projects already don't use them - saves us from pointless churn - git keeps history for us - the year range is kept in COPYING checksrc is updated to allow non-year using copyright statements Closes #10205
33 lines
1.3 KiB
Makefile
33 lines
1.3 KiB
Makefile
c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
|
|
SPDX-License-Identifier: curl
|
|
Long: location
|
|
Short: L
|
|
Help: Follow redirects
|
|
Protocols: HTTP
|
|
Category: http
|
|
Example: -L $URL
|
|
Added: 4.9
|
|
See-also: resolve alt-svc
|
|
Multi: boolean
|
|
---
|
|
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
|
|
--include or --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 will not 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 if the request is a POST, it will send 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.
|
|
|
|
You can tell curl to not change POST requests to GET after a 30x response by
|
|
using the dedicated options for that: --post301, --post302 and --post303.
|
|
|
|
The method set with --request overrides the method curl would otherwise select
|
|
to use.
|