proxy problems with 2.0.5

[Alan DeKok]

  Ah  You're relying on the "authorize" section being run after the
proxy reply is received.

  Don't do that.

  That feature was removed before 2.0, and seems to have accidentally
been enabled again.  It was removed in 2.0.5 because it's wrong.  The
"post-proxy" section is meant to process proxy replies.  Use it, not the
"authorize" section.

  If you need to run some *specific* module in the post-proxy section,
you can migrate your configuration by doing:

post-proxy {
	...
	files.authorize
	sql.authorize
	...
}

  Which will run the "authorize" sections of the "files" and "sql" modules.

  Alan DeKok.