> > 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
On Thu, Jan 23, 2014 at 06:55:04AM -0500, AD7six wrote:
Hi there,
> Allow me to rephrase: Is there a way to define rules for static files -
> without that causing problems for dynamic requests matching the same url
> pattern?
Asking the question that way, the answer is probably "no".
Whatever r
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
On Wed, Jan 22, 2014 at 09:07:13PM +, Jonathan Matthews wrote:
> On 22 January 2014 20:36, Francis Daly wrote:
> > On Wed, Jan 22, 2014 at 02:54:35PM -0500, AD7six wrote:
Hi there,
> >> location ~ \.php$ {
> >> location ~* \.(?:manifest|appcache|html?|xml|json)$ {
> >> An invalid re
On Wednesday 22 January 2014 21:07:13 Jonathan Matthews wrote:
[..]
> ... and its this last step which isn't working as expected. I don't
> quite have the explanation or docs to hand to say why this won't work,
> but this SO page seems to have an interestingly un-up-voted answer at
> the bottom of
On 22 January 2014 20:36, Francis Daly wrote:
> On Wed, Jan 22, 2014 at 02:54:35PM -0500, AD7six wrote:
>
> Hi there,
>
>> location ~ \.php$ {
>> location ~* \.(?:manifest|appcache|html?|xml|json)$ {
>
>> A valid response where the url is a file:
>>
>> $ curl -i http://nginx.dev/foo.json
>
On Wed, Jan 22, 2014 at 02:54:35PM -0500, AD7six wrote:
Hi there,
> location ~ \.php$ {
> location ~* \.(?:manifest|appcache|html?|xml|json)$ {
> A valid response where the url is a file:
>
> $ curl -i http://nginx.dev/foo.json
> HTTP/1.1 200 OK
> An invalid response when passed to php
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. Onl
On 22 January 2014 18:31, AD7six wrote:
> 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 seen in the log [3] there is an invalid response from /index.php.
> If I disable the location block addi
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://ngin
10 matches
Mail list logo
