is there a way to avoid output body when a request is calling for a
vhost
that not exist?
Normally when user send a request to nginx server for a server name
doesn’t
exits on nginx server, nginx will reply “Bad Hostname”.
If you (me) add following lines :
server {
listen 80;
server_name _;
location / {
return 404;
}
}
some cases of nginx return 404, some return 403.
And in all cases, nginx return a html error page with error message in
body.
Is there a way just return 404 and do not return any more error message
when
user request for a server name which does not exist? OR EVEN BETTER,
just
don’t return anything like the server is dead to those request?
Thanks for any suggestion. I love nginx.
On Sun, Dec 06, 2009 at 01:27:31AM +0800, tOmasEn wrote:
server_name _;
user request for a server name which does not exist? OR EVEN BETTER, just
don’t return anything like the server is dead to those request?
Thanks for any suggestion. I love nginx.
http://nginx.org/docs/http/request_processing.html#how_to_prevent_wrong_server_names
–
Igor S.
http://sysoev.ru/en/
Great. Thanks
But then another question popup:
When use proxy_pass , if the backend server use above technique. The
front-end server will return 502 error and error message html.
Is there an easy way do avoid such output?
might not be I guess. It’s
a
bit of tricky
On Sun, Dec 06, 2009 at 12:38:01PM +0800, tOmasEn wrote:
Great. Thanks
But then another question popup:
When use proxy_pass , if the backend server use above technique. The
front-end server will return 502 error and error message html.
Is there an easy way do avoid such output?
might not be I guess. It’s a
bit of tricky
You should use this server at frontend.
As to your question:
error_page 502 = @444;
location @444 { return 444; }
some cases of nginx return 404, some return 403.
[email protected]
nginx Info Page
–
Tomasen
http://twitter.com/ShooterPlayer
nginx mailing list
[email protected]
nginx Info Page
–
Igor S.
http://sysoev.ru/en/