Welcome! Log In Create A New Profile

Advanced

Re: Good Directive vs Bad Directives

Francis Daly
May 02, 2012 07:40AM
On Tue, May 01, 2012 at 06:34:57PM -0700, antituhan wrote:

Hi there,

> Ok, basicly it's just a different directive (simple and 'crowded'
> directive), isn't it ?

It's a different directive, that does different things.

> So, the conclusion is that "if"
> directive is same as "try_files", the different is only on the simplicity,
> and it's not causing cpu/mem high load, right?

"if" can do a lot more than try_files, but has its own pitfalls when
used within location{}.

If what you want is "if this file exists, process it; otherwise do this
other thing", that is what try_files is for.

f
--
Francis Daly francis@daoine.org

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

Good Directive vs Bad Directives

antituhan April 24, 2012 11:32AM

Re: [ASK] Good Directive vs Bad Directives

antituhan April 30, 2012 05:28PM

Re: Good Directive vs Bad Directives

Francis Daly May 01, 2012 01:44PM

Re: Good Directive vs Bad Directives

antituhan May 01, 2012 09:36PM

Re: Good Directive vs Bad Directives

Cliff Wells May 01, 2012 09:48PM

Re: Good Directive vs Bad Directives

Francis Daly May 02, 2012 07:40AM

Re: Good Directive vs Bad Directives

antituhan May 03, 2012 09:06AM

Re: Good Directive vs Bad Directives

Francis Daly May 03, 2012 06:28PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 150
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready