Re: Understanding location blocks and try files

> > I did also try using the front controller as a 404 handler which worked > > exactly how I am trying to get things to work _except_ of course everything > > from the front controller is a http 404. > Why "of course"? > http://nginx.org/r/error_page I said "of course" as when processed as a 40

Re: Understanding location blocks and try files

Hey, thanks for the responses! Indeed your input has been very insightful, some follow ups: @Jonathan/@Valentin Your analysis is about right, the linked prior posts on the mailing list were very informative. @Francis > > An invalid response when passed to php: > > >$ curl -i http://nginx.dev/app

Re: Understanding location blocks and try files

same url pattern? Cheers, AD [1] https://github.com/AD7six/server-configs-nginx/blob/location-debug/sites-available/nginx.dev Posted at Nginx Forum: http://forum.nginx.org/read.php?2,246713,246718#msg-246718 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Understanding location blocks and try files

t as to why this happens? Is there a way to define location blocks for static files - without that causing problems for dynamic requests for the same url pattern? Any help appreciated, Cheers, AD [1] https://github.com/AD7six/server-configs-nginx [2] https://gist.github.com/AD7six/eafe7c