Re: Request for a "no capture" rewrite directive enhancement

2014-05-28 Thread Peter Mescalchin
x would rather be (?...), > as perlre docs <http://perldoc.perl.org/perlre.html#Extended-Patterns >state. > Then, just use you first syntax (omitting the 'set' directives). > --- > *B. R.* > > > On Wed, May 28, 2014 at 12:02 PM, Igor Sysoev wrote: > >

Re: Request for a "no capture" rewrite directive enhancement

2014-05-27 Thread Peter Mescalchin
Thanks Igor, I had explored that method already, sadly (as you know) "alias" is given as an absolute path meaning I can't use this block of config within multiple virtual hosts which I include; - would have to re-write this same block of config for each Virtual host modifying the alias path pre

Re: Request for a "no capture" rewrite directive enhancement

2014-05-27 Thread Peter Mescalchin
Thanks for the reply BR. That's not quite what I'm after - "rewrite" does an internal redirect, "return" will tell the browser to redirect. This recipe is all about CSS/JS "cache busting" of requested assets. Make sense? > What about: > > location ~ "^/[a-f0-9]{16}/(css|js)/(.+)" { > >

Request for a "no capture" rewrite directive enhancement

2014-05-27 Thread Peter Mescalchin
Hello Nginx developers, speaking to Maxim Konovalov over Twitter, suggested this would be the better place to get an answer to my suggestion. Basically what I would like to see is the ability to use a rewrite directive without the need to capture the current URI, which in turn overwrites $1,$2