<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Having 'elseif' / 'else' blocks as well as 'if' would be handy too.
It's obviously possible with lots of 'if' statements, but isn't the
most efficient way of doing things.<br>
<br>
Marcus.<br>
<br>
<br>
mike wrote:
<blockquote
cite="mid:bd9320b30903180826r209e292re39fdf2a495d5b8a@mail.gmail.com"
type="cite">
<pre wrap="">2009/3/18 Igor Sysoev <a class="moz-txt-link-rfc2396E" href="mailto:is@rambler-co.ru"><is@rambler-co.ru></a>:
</pre>
<blockquote type="cite">
<pre wrap="">This is a reference and some cookbook recepts but not introdution.
I can write draft description of request processing from confuguration
point of view but without these ugly rewrites as want to change them.
</pre>
</blockquote>
<pre wrap=""><!---->
When you say "ugly rewrites" what do you mean?
IMHO, nginx is pretty easy to pick up. At first when I saw the syntax
I thought "oh no, another config file to learn" but it is pretty damn
simple.
My biggest issue is with location blocks. It is still confusing and
gets annoying on sites requiring multiple location blocks, especially
with regexps and determining the right ^~ or *~ etc.
Other than that, a few tweaks to allow things like error_log at -any-
level not just global and server but even inside conditionals would be
neat...
But I'm wondering what you meant by that. You have some code you don't
like in nginx that you want to rewrite? If so, what? Or the "rewrite"
directive itself and such is a nasty thing. I like to hear the plans
and news about nginx (call me an nginx fanboy now) - even a roadmap
would be cool too (I think I've seen bits and pieces in the past) of
what at least you plan on changing/adding, and of course if other
people do third party modules or patch things in the core that can
only enhance it quicker...
</pre>
</blockquote>
<br>
</body>
</html>