<div class="gmail_quote">On 8 April 2011 04:32, Maxim Dounin <span dir="ltr"><<a href="mailto:mdounin@mdounin.ru" target="_blank">mdounin@mdounin.ru</a>></span> wrote:</div><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
There were lots of such discussions, and the only expected answer<br>
to all proposals to add global/continue/whatever locations which<br>
alter configuration is: no.<br>
<br>
The reason is simple: with large config it's practically<br>
impossible to find out how requests will be processed when<br>
such "global" locations are present.</blockquote><div><br></div><div>I should have been clear -- global/continue/whatever are not the same thing. A "continue" location is tested in the normal order. This means there's a possibility it's _not_ processed even if it matches, if it comes after a normal match-and-break location in nginx's testing order.</div>
<div><br></div><div>Assuming you meant what I did by "continue", I'm not sure whether you are saying simply that it's difficult for users to understand such configs, or whether you're saying the processing actually is undefined. </div>
<div><br></div><div>If it's the former, then, is it not the case that:</div><div><br></div><div>a) (likely very many) large configs wouldn't be so large if they used "continue" locations</div><div>b) the cheapest alternative is nested locations, which are themselves difficult to understand, and</div>
<div>c) existing users need not implement it</div><div><br></div><div>The idea is to simplify the configs of new and ordinary users, and to provide a compact alternative to common nesting motifs.</div>
<div><br></div><div>If on the other hand you are saying that there are cases where processing somehow becomes undefined when using a "continue" location, can you provide an example (which does not occur for an equivalent nested directive)?</div>
<div><br></div><div>Thomas</div>
</div>