Of course I thought about it, but I still have limit_conn and is not related to static files. So far what I've done for all the static files directory eg /static/.
However, due to these files as favicon.ico, robots.txt, sitemap.xml configuration of Nginx to grow. Not only that I have to repeatedly reproduce the path to the root. Maybe "set" to solve this problem, but I thought that this approach of $request_filename is more convenient. I see not much bigger security risks ? Would be nice to see on the wiki complete sample configuration Nginx + uwsgi + static files (such as favicon.ico, robots.txt /images/) On Wed, 25 Aug 2010 13:31:44 +0200, Roberto De Ioris <[email protected]> wrote: > > Il giorno 25/ago/2010, alle ore 12.59, Łukasz Wróblewski ha scritto: >> >> >> >> Unfortunately, I have: >> Restarting nginx: [emerg]: "include" directive is not allowed here in line 7. >> >> would it not be able to do "include" inside "if" ?! >> any advice ? >> >> >> > > Put the include line out of the if statement, the only relevant option is > uwsgi_pass. > > By the way, i am not a big fan of the rubyonrails-like static file rule, i > find defining a location for every static > directory a better (and more secure) way. > -- > Roberto De Ioris > http://unbit.it > JID: [email protected] > > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > -- Łukasz Wróblewski DDarko.org www.hostowisko.pl - profesjonalny i tani hosting www.nri.pl - nowoczesne rozwiązania internetowe www.katalog-polskich-firm.pl - najlepszy darmowy katalog firm _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
