Hi all,

Krzysztof Oledzki managed to make dev7 reliably crash. After
investigation, it appeared that one of the latest keep-alive
bugs I had fixed was not complete as the same code was present
in another function.

In practice, 1.4-dev5, -dev6 and -dev7 are affected by the same
bug and may randomly crash in http-server-close mode (or corrupt
part of their memory) when users are running at low speed with
pipelined requests and that the server is very fast, and many
headers are added or rewritten in the response.

So I'm releasing 1.4-dev8 with that nasty bug fixed, so that
people don't take useless risks and we can make a difference
between that bug and any possibly new one in bug reports.

A few other minor issues were fixed (eg: don't forward invalid
pending response data when closing a keep-alive connection).
Cyril Bonté also did a nice review of config options in the doc
versus the parser in order to fix both to make them agree.

Last, some of you may be aware that most browsers and proxies
use the non-standard HTTP header Proxy-Connection instead of
Connection when talking on proxied connections. This one
requires special handling as such non-conform HTTP agents
simply ignore the Connection header which is still the only
one defined by the spec. So I have added an option for
frontends for those who want to deploy haproxy in front
of a proxy farm with keep-alive. This option allows haproxy
to automatically detect proxied connections (URL does not
start by '/' nor '*') and switch to Proxy-Connection instead
of Connection. I don't recommend enabling that by default
when not needed.

Well, hopefully this time 1.4-dev8 will be reliable...

It's available at the usual place :

   http://haproxy.1wt.eu/download/1.4/src/
   http://haproxy.1wt.eu/download/1.4/src/haproxy-1.4-dev8.tar.gz
   http://haproxy.1wt.eu/download/1.4/src/CHANGELOG
   http://haproxy.1wt.eu/download/1.4/doc/configuration.txt

Please report any regression or issue you may observe. And
keep in mind that it MUST NOT crash, never ever. If it ever
does, please complain here loudly with maximum information.

Thanks,
Willy


Reply via email to