Stuck with curl maximum redirects followed? We can help you.
Here at Bobcares, we have seen several such curl command related errors as part of our Server Management Services for web hosts and online service providers.
Today we’ll take a look at the causes for this error and see the fix.
Know more about curl redirect
curl is a command-line program. Also, it allows you to send any type of HTTP request via the command line.
We can see the actual redirect using curl. For instance,
curl example.com
#<HTML><HEAD><meta http-equiv=”content-type” content=”text/html;charset=utf-8″>
#<TITLE>301 Moved</TITLE></HEAD><BODY>
#<H1>301 Moved</H1>
#The document has moved
#<A HREF=”http://www.example.com/”>here</A>.
#</BODY></HTML>Using bash scripts or while running curl via command line manually, it is not necessary to handle these redirects manually. Or else, it can add a lot of unnecessary logic to your script.
Because of this, cURL provides a command-line flag that tells it to automatically follow the redirect and return the resolved endpoint and its data:
$ curl -L [url]The above command will automatically handle any 3XX redirects and will retrieve whatever data is returned by the resulting URL.
Also, it instructs cURL to follow any redirect so as a result, you reach the exact endpoint.
What causes curl maximum redirects followed to occur
Now, let’s see the causes for this error to occur.
In some cases, on accessing some sites using curl, it fails after 50 redirects.
curl ‘example.com’ -L -o ‘output.txt’As a result, it throws the below error message:
curl: (47) Maximum (50) redirects followed
No data in the output.txt file.
This error occurs because of :
1. By default, cookies are not enabled in curl.
2. Curl has a way to handle redirects by enforcing a maximum number of redirects it will follow. By default, it is 50.
How we fix curl maximum redirects followed error
Now let’s see the solution part of this error. Here are the steps that our Support Engineers provide to our customers to fix this error.
1. Try accessing the same website using wget command and check whether the same error occurs. In case, if wget don’t throw any error then it means that curl is not asked to use cookies, which it does not do unless it is mentioned while wget enables them by default.
Use the –cookie or –cookie-jar options to enable cookies.
curl -v –cookie “USER_TOKEN=Yes” http://example.com/
curl -v –cookie-jar cookie_file http://example.com/In the backend, we can view the value by using:
print request.cookies2. Make use of the –max-redirs option, maximum redirect value can be set. On the other hand, if you don’t want a limit at all, then just set it to -1.
[Need any further assistance in fixing curl errors? – We are here to help you.]
Conclusion
In short, this error occurs if cookies are not set in curl or if the maximum number of redirects exceeds. Today, we saw how our Support Engineers fix this error.
0 Comments