Nginx HttpAccessModule command invalid when rewrite command existed
li zJay
zjay1987 at gmail.com
Wed Nov 9 14:58:13 UTC 2011
Thanks Igor. That is OK, and I had a think and use the following commands
instead:
location /entry1 {
if ( ! $remote_addr ~ "^(127\.0\.0|10\.10\.10)" ) { return 403; }
rewrite ***
}
On Wed, Nov 9, 2011 at 10:42 PM, Igor Sysoev <igor at sysoev.ru> wrote:
> On Wed, Nov 09, 2011 at 10:35:44PM +0800, li zJay wrote:
> > In the following simple case:
> >
> > location /entry1 {
> > allow 127.0.0.1;
> > deny all;
> > rewrite ***;
> > }
> >
> > the allow/deny command has no effect. Is that because rewrite command
> works
> > in the earlier phase?
>
> Yes, rewrites run before allow/deny.
>
>
> --
> Igor Sysoev
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20111109/ca830659/attachment.html>
More information about the nginx
mailing list