> I'm not a big fan of the location that sets the 418 error_page to the
> @foo_front_controller named location, but I don't know of any other way
> to essentially do a "return @foo_front_controller". Is there a better
> way?
Use "try_files" instead with a filename that will never exist (i.e.
Hello, nginxers!
What's the best way to server static content as well as dynamic content
that uses the Front Controller pattern under the same base URI?
I'm dealing with a web app partially written in PHP that expects to
serve static content as well as dynamic PHP content, using the Front
