> Exact locations are faster.
Thanks again. We will go with exact locations. :-)
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,248659,249046#msg-249046
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Apr 4, 2014, at 16:05 , rahul286 wrote:
> @Igor
>
> Few Updates:
>
>> location = old-url-1 { return 301 new-url-1; }
>
> is really nice. We can specify 301/302 using it.
>
> But I am reading -
> http://nginx.org/en/docs/http/ngx_http_fastcgi_module.html#fastcgi_cache_valid
> and now I am th
@Igor
Few Updates:
> location = old-url-1 { return 301 new-url-1; }
is really nice. We can specify 301/302 using it.
But I am reading -
http://nginx.org/en/docs/http/ngx_http_fastcgi_module.html#fastcgi_cache_valid
and now I am thining weather to populate config file with 1000's of lines
like b
Igor Sysoev Wrote:
---
> location = old-url-1 { return 301 new-url-1; }
Bingo! Never thought of this. :-)
We will use this for https://github.com/rtCamp/easyengine/issues/162
Thanks a lot. :-)
Posted at Nginx Forum:
http://forum.nginx.org/rea
On Mar 25, 2014, at 12:12 , rahul286 wrote:
> Hi All,
>
> I am just wondering, say for 1000 url redirects, what will be more
> efficient.
>
> Rewrite Style:
>
> server {
> rewrite old-url-1 new-url-1 permanent;
> rewrite old-url-2 new-ur
Hi All,
I am just wondering, say for 1000 url redirects, what will be more
efficient.
Rewrite Style:
server {
rewrite old-url-1 new-url-1 permanent;
rewrite old-url-2 new-url-2 permanent;
rewrite old-url-3 new-ur
