2.1.12 bug/change in behaviour - un-named server {} blocks no longer work?

[Alan DeKok]

Phil Mayers wrote:
> 2.1.12 seems to not process this config; it seems to completely ignore
> the un-named virtual server config:

  Hmm.. OK

> ...and thus nothing works. AFAICT this is a change from 2.1.10/11
> (although I was always running a "pre-release" i.e. a known-good commit)

  Weird...

> Removing the un-named:
> 
> server {
> }
> 
> enclosing blocks makes everything work again.
> 
> I haven't had time to hunt down the commit which might have changed
> this, but just a heads-up.

  I've pushed a fix <sigh>

  Alan DeKok.