14 messages in ru.sysoev.nginxRe: Rewriting https to http
FromSent OnAttachments
iane...@public.gmane.orgJan 11, 2007 1:26 pm 
Igor SysoevJan 11, 2007 1:40 pm 
Jonathan DanceJan 12, 2007 3:56 am 
Jonathan DanceJan 12, 2007 4:06 am 
Igor SysoevJan 12, 2007 4:16 am 
Igor SysoevJan 12, 2007 4:32 am 
Jonathan DanceJan 12, 2007 4:33 am 
Jonathan DanceJan 12, 2007 4:40 am 
Igor SysoevJan 12, 2007 4:42 am 
Igor SysoevJan 12, 2007 4:45 am 
Jonathan DanceJan 12, 2007 5:20 am 
Igor SysoevJan 12, 2007 5:35 am 
Igor SysoevJan 12, 2007 6:41 am 
Jonathan DanceJan 12, 2007 6:55 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Rewriting https to httpActions...
From:Igor Sysoev (is-G@public.gmane.org)
Date:Jan 12, 2007 4:16:14 am
List:ru.sysoev.nginx

On Fri, 12 Jan 2007, Jonathan Dance wrote:

On that note, one thing I noticed that is ambiguous is the following:

location ^~ /images/ { # config A } location /images/icons/ { # config B }

According to my precedence listing, config B would never be invoked, but would a request to /images/icons/ actually match config B? In other words, if I were add the following...

location ~* "." { # config C }

...would a request to /images/icons/ be handled by A or C?

The nginx finds the most long static location. It would be B for /images/icons/. Then if the regexes is not forbidden by "^~" for this location, nginx finds the first matching regex, and, of course, it would be C.

So in the end the /images/icons/ will be handled by C.

Igor Sysoev http://sysoev.ru/en/