Keywords: curl | redirect | Linux command line
Abstract: This article provides an in-depth exploration of using the curl command in Linux environments to obtain the final URL after webpage redirects. By analyzing the -w option and url_effective variable in curl, it explains how to efficiently trace redirect chains without downloading content. The discussion covers parameter configurations, potential issues, and solutions, offering practical guidance for system administrators and developers on command-line tool usage.
Introduction
URL redirection is a common occurrence in web requests, such as redirecting from http://google.com to http://www.google.com. For system administrators and developers, the need to retrieve only the final URL without the entire page content is growing, especially in automation scripts and monitoring scenarios. This article systematically introduces how to achieve this using the built-in Linux tool curl.
Core Solution: The -w Option in curl
The -w (writeout) option in curl allows users to customize output format, and when combined with the url_effective variable, it directly retrieves the final URL after redirects. The basic command structure is as follows:
curl -Ls -o /dev/null -w %{url_effective} https://example.comHere, -L enables redirect following, -s activates silent mode to suppress extraneous output, -o /dev/null redirects the response body to null device to avoid content interference, and -w %{url_effective} specifies output of the final effective URL.
Parameter Details and Optimization
To ensure command robustness, it is essential to understand the role of each parameter:
-L: Automatically follows HTTP redirects, handling up to 10 redirects by default (adjustable via--max-redirs).-s: Silent mode, preventing progress bars and error messages from interfering with output.-o /dev/null: Discards downloaded content, retaining only URL information.-w %{url_effective}: Output variable that displays the final URL after redirect completion.
For example, when handling potential multiple redirects, add --max-redirs 20 to increase the limit:
curl -Ls -o /dev/null -w %{url_effective} --max-redirs 20 http://example.comPotential Issues and Considerations
While the above method is effective in most cases, potential issues must be noted. It has been suggested to add the -I option to use the HEAD method and avoid downloading content, but this may alter server behavior, as some servers respond differently to HEAD and GET requests or may return errors. Therefore, unless server support is confirmed, using -I is not recommended.
Additionally, intermediate URLs in redirect chains can be obtained via the %{redirect_url} variable, but url_effective is more direct for the final target. In practical applications, error handling should be incorporated, such as using the -f option to fail silently on HTTP errors or checking exit status codes via scripts.
Application Scenarios and Extensions
This technique is widely used in link validation, SEO analysis, and automated testing. For instance, in batch checking URL redirects, scripts can be written to process lists iteratively and log final URLs. Compared to the tool wget, curl offers more flexible output control, although wget's --max-redirect and --spider modes can achieve similar functionality, with curl having advantages in integration and lightweight operation.
Conclusion
Using curl's -w option and url_effective variable, users can efficiently and accurately retrieve the final URL after redirects without downloading redundant content. The method introduced in this article, based on built-in Linux tools, emphasizes parameter configuration and handling of potential issues, providing reliable reference for related technical practices. In actual deployment, it is recommended to adjust parameters based on specific needs and test server compatibility to ensure stability.