Rewriting https to http

[Igor Sysoev]

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/