Use the $remote_addr variable to check against the local IP address, if the visitor isn't local, then send a 503 maintenance page. The 503 code is important so search engines wont mark the website as dead.<br><br><div class="gmail_quote">
On 22 May 2010 00:31, Ian M. Evans <span dir="ltr"><<a href="mailto:ianevans@digitalhit.com">ianevans@digitalhit.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
As I prepare to test some changes related to the "0day exploit" thread, I thought I'd set up a maintenance page block so I could do the testing.<br>
<br>
Just realized though that the maintenance block examples take the site down for everyone.<br>
<br>
How do you serve the maintenance page to visitors will still allowing localhost access.<br>
<br>
Should I just create a new server block listening on another port and deny all, allow 127.0.0.1?<br>
<br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org" target="_blank">nginx@nginx.org</a><br>
<a href="http://nginx.org/mailman/listinfo/nginx" target="_blank">http://nginx.org/mailman/listinfo/nginx</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Kind Regards,<br>-Mathew Davies.<br>