Welcome! Log In Create A New Profile

Advanced

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

Peter Mescalchin
May 28, 2014 12:34AM
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;
> return $scheme://$host/$1/$2? break;
> }
>
> ?
>
> You could add the 301 code for permanent redirect, see
> http://nginx.org/r/return
> ---
> *B. R.*
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

Request for a "no capture" rewrite directive enhancement

Peter Mescalchin May 27, 2014 07:54PM

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

B.R. May 28, 2014 12:04AM

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

Peter Mescalchin May 28, 2014 12:34AM

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

Igor Sysoev May 28, 2014 12:46AM

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

Peter Mescalchin May 28, 2014 12:56AM

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

Igor Sysoev May 28, 2014 06:04AM

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

B.R. May 28, 2014 11:42AM

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

Igor Sysoev May 28, 2014 12:12PM

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

Peter Mescalchin May 28, 2014 10:10PM

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

B.R. May 28, 2014 10:48PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 167
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready