-
Notifications
You must be signed in to change notification settings - Fork 53
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
Host header is specified and is not an IP address or localhost. #40
Comments
I have the same issue |
Can you provide more details? Are you having this issue in the chrome version or the selenium version? |
This seems to be a known issue with Chrome 66, but I'm struggling to find how to workaround it, more details: |
The only suitable workaround I've found is to pin to the last known version of chrome where this problem didn't exist |
@yukinying any possible way to use proxy inside the image? proxy catches incoming requests and send to chrome instance, the proxy and chrome instance in the same docker container |
@hbakhtiyor Also you can map docker host IP to /etc/hosts and connect to a chrome instance via created host name, this issue about only if you use IP |
hi @wholegroup, the issue is that the same ip address uses for many subdomains (which has different instances) |
@hbakhtiyor I can't see your configuration, but still I don't see any problems. before
after
/etc/hosts on a client
It is almost the same. |
same issue with chromium 72 when a request by domain. with ip ok, |
bool RequestIsSafeToServe(const net::HttpServerRequestInfo& info) {
// For browser-originating requests, serve only those that are coming from
// pages loaded off localhost or fixed IPs.
std::string header = info.headers["host"];
if (header.empty())
return true;
GURL url = GURL("http://" + header);
return url.HostIsIPAddress() || net::IsLocalHostname(url.host(), nullptr);
} if (!RequestIsSafeToServe(info)) {
Send500(connection_id,
"Host header is specified and is not an IP address or localhost.");
return;
} why domain not safe? |
Hello, |
I am running into this issue when attempting to load balance NGINX upstream to a set of chrome headless pods. I am invoking the CDP commands externally from a different docker container. @m7shapan can you advise on where exactly the above workaround can be implemented? alternatively, Is there any flag directly that can resolve this in the more recent releases? |
getting this error in the latest of stable chrome
The text was updated successfully, but these errors were encountered: