-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
The URL is invalid: two slashes are needed after the http(s):. #417
Comments
Same issue! I´m using Azure Cloud |
You have something else running in front of CORS Anywhere that normalizes the URLs. You should disable that URL rewriting mechanism, to preserve the original request URL. If that is not possible at all, an alternative is to omit the scheme. From a quick search, it seems that Plesk uses Apache. See https://github.com/Rob--W/cors-anywhere/issues/308 For Azure Cloud, see #82. |
Thank you for pointing me in the right direction, turning off nginx proxy mode under nginx settings solves the issue in Plesk. |
Cloudflare Workers W3C URL JS class has a well known bug that turns "//" into "/" . The CF bug can be googled. |
please guide vercel also |
If this is useful for someone Here is a config for nginx
|
On PaaS platforms (e.g. Heroku) where there is no "nginx" to configure, add a check before cors-anywhere/lib/cors-anywhere.js Line 312 in 70aaa22
|
Hello,
I have managed to get cors-anywhere setup on my plesk server :)
But I seem to be running into an issue I cannot figure out, no matter what URL I use I am presented with the error:
" The URL is invalid: two slashes are needed after the http(s):. "
This error shows no matter what URL I try to access for example:
https://mycorsproxy.url/http://google.com
https://mycorsproxy.url/https://google.com
Am I missing something obvious here?
Any help is much appreciated, thank you!
The text was updated successfully, but these errors were encountered: