> > 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 404 - it didn't seem possible to modify the http reby AD7six - Nginx Mailing List - English
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/apples.json > > HTTP/1.1 404 Not Found > Why do you think that thiby AD7six - Nginx Mailing List - English
Thanks for the reply, I've read through those sections again - if I'm missing something obvious I'm afraid I need someone to point it out to me :| Sorry about that I thought pointing at a working example would allow close scrutiny - didn't think to remove the files/config that weren't in use. Only the mentioned location block is relevant, inlining that and the fastcgi config becomes [1]:by AD7six - Nginx Mailing List - English
Hi, I'm trying to understand a problem I'm facing in a typical frontend-controller application. I've setup a test config with a single simple server [1], and ran a test script with debugging enabled to show what happens [2]. What confuses me is why this example is a 404: > curl -i http://nginx.dev/apples.json > HTTP/1.1 404 Not Found > Server: nginx/1.4.4 As can be sby AD7six - Nginx Mailing List - English