Answer the question
In order to leave comments, you need to log in
How to prevent the return of information about the https certificate when it does not match?
The question in the header sounds vague, but here is a specific example:
This is https on the ip of the first answer nslookup toster.ru. On my host, the situation is one to one - i.e. if the host does not exist for nginx, or if the ip is accessed via https - nginx cannot answer something because the browser refuses to establish a connection because the certificate does not match. And it makes sense, yes. Is it possible to prevent such behavior?
Answer the question
In order to leave comments, you need to log in
It is possible only from the side of the client, which performs the check.
For chrome, for example, you can run it with the --ignore-certificate-errors parameter.
From the host side, you can’t do it in any way.
It is possible to prevent a situation in which the user accidentally gets through the browser to a non-existent HTTPS URL, only purposefully.
IMHO, you don't have to do anything about it. You can probably parse the Host header before establishing a connection and break the connection, for example, but the purpose is not very clear.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question