I think Igor is suggesting PERL named captures.
Although, it appears to me the correct syntax would rather be (?name...),
as perlre docs http://perldoc.perl.org/perlre.html#Extended-Patternsstate.
Then, just use you first syntax (omitting the 'set' directives).
---
*B. R.*
On Wed, May 28, 2014
On 28 May 2014, at 19:39, B.R. reallfqq-ng...@yahoo.fr wrote:
I think Igor is suggesting PERL named captures.
Although, it appears to me the correct syntax would rather be (?name...),
as perlre docs state.
Then, just use you first syntax (omitting the 'set' directives).
You a re right, I
Fantastic Igor - I didn't know that you could do named captures in Nginx -
good to know.
That solves it rather nicely.
And thanks B.R. - yep, that syntax is part of PCRE.
Pete
I think Igor is suggesting PERL named captures.
Although, it appears to me the correct syntax would rather be
Yup the location directive uses the PCRE library to interpret regex.
Its docs doesn't mention that the regex are PCRE, but the hint is given
away on the build from sources http://nginx.org/en/docs/configure.htmlpage.
It reminds me that not so long ago I mixed up named captures and
subpatterns
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
What about:
location ~ ^/[a-f0-9]{16}/(css|js)/(.+) {
expires 30d;
return $scheme://$host/$1/$2? break;
}
?
You could add the 301 code for permanent redirect, see
http://nginx.org/r/return
---
*B. R.*
On Wed, May 28, 2014 at 1:52 AM, 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)/(.+) {
expires 30d;
On 28 May 2014, at 03:52, Peter Mescalchin peter.mescalc...@gmail.com wrote:
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
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
