Re: NGINX Location Matching Question - Case insensitive matching at the start of a URI

2013-12-05 Thread Brad Van Sickle
Thanks for the quick response! Looks like that is matching how I intend... however it (of course) revealed another issue in my app layer :) But at least the NGINX configs seems correct now. Thanks! On 12/5/2013 6:40 PM, Jonathan Matthews wrote: On 5 December 2013 23:29, Brad Van Sickle w

Re: NGINX Location Matching Question - Case insensitive matching at the start of a URI

2013-12-05 Thread Jonathan Matthews
On 5 December 2013 23:29, Brad Van Sickle wrote: > > Hi, > > I'm running in a somewhat urgent issue where I have to make a > case-insensitive location match on a URI segment that is at the > beginning of the URI. > > so I want to match > > /uri-segment/* > /URI-segment/* > /Uri-Segment/* > etc.. >

NGINX Location Matching Question - Case insensitive matching at the start of a URI

2013-12-05 Thread Brad Van Sickle
Hi, I'm running in a somewhat urgent issue where I have to make a case-insensitive location match on a URI segment that is at the beginning of the URI. so I want to match /uri-segment/* /URI-segment/* /Uri-Segment/* etc.. I know that this will match the start of the URI: location ^~ /uri-segm

Re: location matching.

2013-05-13 Thread Francis Daly
location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ { and, of those, this request should be handled in the first one. But you report that it is actually handled in the second. As well as the location{} blocks, there are server-level rewrites and if() blocks, which will take effect before the location-

Re: location matching.

2013-05-12 Thread Steve Wilson
The good news is it looks like subversion clients support SNI so I've got a new server block which is now working great. server { listen 80; ## listen for ipv4 listen 443; ## listen for ipv4 listen [::]:80; ## listen for ip

Re: location matching.

2013-05-12 Thread Steve Wilson
On 12/05/2013 16:34, Jonathan Matthews wrote: > On 12 May 2013 16:21, Steve Wilson wrote: >> On 12/05/2013 15:55, Jonathan Matthews wrote: >>> Have you looked at the ^~ prefix mentioned in >>> http://wiki.nginx.org/HttpCoreModule#location ? >>> >>> It looks like what you need ... >> >> I thought

Re: location matching.

2013-05-12 Thread Jonathan Matthews
On 12 May 2013 16:21, Steve Wilson wrote: > On 12/05/2013 15:55, Jonathan Matthews wrote: >> Have you looked at the ^~ prefix mentioned in >> http://wiki.nginx.org/HttpCoreModule#location ? >> >> It looks like what you need ... > > I thought I'd tried that, and even with the change in config it's

Re: location matching.

2013-05-12 Thread Steve Wilson
On 12/05/2013 15:55, Jonathan Matthews wrote: > Have you looked at the ^~ prefix mentioned in > http://wiki.nginx.org/HttpCoreModule#location ? > > It looks like what you need ... I thought I'd tried that, and even with the change in config it's still giving me the 404 errors. changed config:

Re: location matching.

2013-05-12 Thread Jonathan Matthews
Have you looked at the ^~ prefix mentioned in http://wiki.nginx.org/HttpCoreModule#location ? It looks like what you need ... -- Jonathan Matthews // Oxford, London, UK http://www.jpluscplusm.com/contact.html ___ nginx mailing list nginx@nginx.org htt

location matching.

2013-05-12 Thread Steve Wilson
I've just had to move subversion onto a server that's already serving network wordpress via nginx. Most things work via /svn in a subversion client but I can't for the life of me figure out how to stop /svn.*\.php hitting the fastcgi_pass. I'm sure it's simple and I'm just not seeing the wood for