Re: Removing blank location block causes 404 errors

2014-03-20 Thread Francis Daly
On Thu, Mar 20, 2014 at 04:33:35PM -0400, drhowarddrf...@charter.net wrote: Hi there, > I was just typing what I think may be the reason. That other location > blocks may be picking this up and eventually returning a 404 but, with > that block in there, the image and css requests are getting "h

Removing blank location block causes 404 errors

2014-03-20 Thread drhowarddrfine
I was just typing what I think may be the reason. That other location blocks may be picking this up and eventually returning a 404 but, with that block in there, the image and css requests are getting "handled", ie, nothing is done to them at all, and then retrieved from their proper director

Re: Removing blank location block causes 404 errors

2014-03-20 Thread Francis Daly
On Thu, Mar 20, 2014 at 04:10:29PM -0400, drhowarddrf...@charter.net wrote: Hi there, > location ~* > ^.+\.(css|js|jpg|jpeg|gif|png|ico|gz|svg|svgz|ttf|otf|woff|eot|mp4|ogg|ogv|webm|pdf)$ > > { > } > > Today, I deleted that block and now the images, css and javascript files > are all returne

Removing blank location block causes 404 errors

2014-03-20 Thread drhowarddrfine
I'm new to nginx and had this in my conf file which I had copied some time ago but never filled it in and continued building a test page with images, css and javascript: location ~* ^.+\.(css|js|jpg|jpeg|gif|png|ico|gz|svg|svgz|ttf|otf|woff|eot|mp4|ogg|ogv|webm|pdf)$ { } Today, I deleted