Re: misunderstood regex location

2014-05-06 Thread dcaillibaud
this sentence is not so clear... > I understand > that all first level are evaluated to see if one branch need to be > explored deeper, but it's not so obvious. ...I mean : I understand that all first level selectors are compared to see which block need to be evaluated deeper, but it's not so o

Re: misunderstood regex location

2014-05-06 Thread dcaillibaud
> > 2) (I guess E but I'm not so sure), this can also be a pitfall > example (how > > complicating things can lead to unexpected behaviour) > > > > location /images/ { > > location ~* \.(gif|jpg|jpeg)$ { > > [ configuration D ] > > } > > } > > > > location ~* \.(gif|jpg|jpeg)$ { > >

Re: misunderstood regex location

2014-05-06 Thread dcaillibaud
I understand my mistake, thanks to both of you. May I suggest to insist on this in http://nginx.org/en/docs/http/ngx_http_core_module.html#location, with a remark on the fact that ^~ is not usable with a regex, for example with syntax: location [ = | ^~ ] uri { ... } location ~ | ~* reg

misunderstood regex location

2014-05-05 Thread dcaillibaud
Hi, I understood that prefix location was read, then regex location and it stops on a ^~ match Why with this config location / { location ~ .+\.(js|css|ico|png|gif|jpg|jpeg|pdf|zip|html|htm)$ { expires 25h; } } location ^~ /banniere_rotative/