There is an `allow all` in a location block, but i would recommend that you
determine what part of All is really needed from your Apache config and
apply only those rules that need to make the site work. I used apache in
exactly this nature for a while and then dug in and found that i only
needed one or two of the directives that can go after AllowOverride. This
is not direct help i realize but comparing what allow all does and
AllowOverride All does will allow you to make the best, most secure choice
for your environment, the default is None and so many configurations change
this to All for a quick fix, but when changing webservers, give it a second
though.

location ~ /blah/fe {
allow all;
}


I found that i never had to use this in nginx except for serving
lets-encrypt certs out a directory, in nginx, but i use it more of a proxy
for scala apps.

Jeff

On Sun, Feb 12, 2017 at 8:19 AM, Daniel <daniel@linux-nerd.de> wrote:

> Hi there,
>
> i still moving from Apache to nginx.
>
> I have a config part in apache which i dont understand how to convert it
> correct to nginx.
>
>
> <Directory /var/www/vhosts/blah/fe>
> RewriteBase /
> Options FollowSymLinks
> AllowOverride All
> DirectoryIndex index.php
> </Directory>
>
> <Directory /var/www/vhosts/blah/fe/static>
> Options +FollowSymLinks -Indexes
> AllowOverride none
> </Directory>
>
> i Know that this has to be done in locations what how? ;)
>
> Cheers
>
> Daniel
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx