access log control while maintaining internal redirection to WordPress

[Igor Sysoev]

On Sep 25, 2012, at 23:12 , Jan-Philip Gehrcke wrote:

> Thanks for your opinion, Igor. Would it also be safe to use `include` statements for blocks that occur multiple times?

Yes, it' safe. Although I prefer not to use "include" for this purpose,
since it complicates the find-and-replace strategy.


--
Igor Sysoev
http://nginx.com/support.html

> Jan-Philip
> 
> On 09/25/2012 10:37 AM, Igor Sysoev wrote:
>> On Tue, Sep 25, 2012 at 10:14:07AM +0200, Jan-Philip Gehrcke wrote:
>>> Thanks, Maxim! This was helpful.
>>> 
>>> However, I'd like to discuss the concept a bit further. We're talking
>>> about changing only one property for a single location while keeping the
>>> rest of the configuration constant -- a pretty common task I guess --
>>> shouldn't there be a more elegant solution?
>> 
>> My exprience of administrating sites with a lot of locations says
>> that it is much better to concentrate complete configuration inside
>> location instead of spreading it across whole file.
>> 
>> When you need to add new functionality in the spreaded configuration
>> you have to check it whole to see possible conflicts. There are no
>> such issues when you add new functionality in configuration with
>> completely separated locations given only location prefixes and
>> without regexes.
>> 
>> The common objection is that you have to dupclicate many common
>> parameters in all these locations. But when you need to change some
>> common parameter in many locations, say upstream address, then
>> find-and-replace in your favourite editor is your friend. It takes
>> far less time to see if a place should be changed or not.