You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we've stumbled upon an inconsistency with the response_code attribute after performing a request with a redirect (with followlocation: true) using a proxy. We're using a Squid proxy.
I've setup a simple redirect to a non-existing page using https://cutt.ly (https://cutt.ly/ayL05Ek -> https://testingcurlfollowlocation.com)
The expected response_code is 503, and the response code returned from Ethon (possibly Curl) is 301 for the redirect. I suspect the issue is that the proxy returns the final error.
Here's the code reproducing the issue (we normally use Typhoeus but I've been able to replicate in Ethon as well, so I'm posting the issue here):
Can you advise on how to modify the request to receive the 503 response_code from Ethon (and possibly Typhoeus as well)? We'd like to refrain from parsing the headers manually.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi, we've stumbled upon an inconsistency with the
response_code
attribute after performing a request with a redirect (withfollowlocation: true
) using a proxy. We're using a Squid proxy.I've setup a simple redirect to a non-existing page using https://cutt.ly (https://cutt.ly/ayL05Ek -> https://testingcurlfollowlocation.com)
The expected
response_code
is 503, and the response code returned from Ethon (possibly Curl) is301
for the redirect. I suspect the issue is that the proxy returns the final error.Here's the code reproducing the issue (we normally use Typhoeus but I've been able to replicate in Ethon as well, so I'm posting the issue here):
The response headers contain the expected response code:
Here's how the response headers look when I use curl directly:
Can you advise on how to modify the request to receive the
503
response_code from Ethon (and possibly Typhoeus as well)? We'd like to refrain from parsing the headers manually.Thanks!
The text was updated successfully, but these errors were encountered: