New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Http proxy append in front of the actual URL | Request failed with status code 503 #1780
Comments
+1 |
Experiencing the same issue with axios@0.18.0 |
+1, Same Issue :( |
Any solution? |
case for me: with the NO_PROXY help could help # fish
set -x NO_PROXY 'typespublisher.blob.core.windows.net' |
See #4209 |
Hi,
I am using axios to fetch response of one of the Api http://xxxxxxxxxxxxxxxxxx.com/actuator/health, I am successfully able to fetch its value from my React Client side code, but when I am setting express endpoint for this at server side and calling below endpoint from the browser
then I am getting below error
Error: Request failed with status code 503
statusText: 'DNS Fail',
host: 'proxy-gcp-central.xxxx.com',
responseUrl: 'http://proxy-gcp-central.xxxx.com/http://xxxxxxxxxxxxxxxxxx.com/actuator/health' ,
_currentUrl: 'http://proxy-gcp-central.xxxx.com/http://xxxxxxxxxxxxxxxxxx.com/actuator/health'
Where http://proxy-gcp-central.xxxx.com/ is append in front of the actual url => hence it is failing
I am getting this issue on cloud environment, I am able to fix this issue on my local by providing proxy information along with url in axios.get function above(as on local I am using proxy server to access this URL), but on cloud we are able to access this directly without use of proxy server, so for cloud, we cannot set this proxy information in this code.
I have tried this with many other node modules like http, request, request-promise, but still I am getting the same issue.
I have also tried to set
Access-Control-Allow-Origin, Access-Control-Allow-Methods, Access-Control-Allow-Headers
in headers as well as in app.use, but none of them resolve my issue.Context
The text was updated successfully, but these errors were encountered: