haproxy (2.6.8-2) unstable; urgency=medium Starting with haproxy 2.6, the "ssl-engine" keyword has been removed. You will need to remove this setting for your previous config to continue to work. Previously, clients sending an invalid request header like "Version: rtsp/1.1" would still get their request being served. Starting with haproxy 2.6, this will result in a 502 response. If you depend on the old, buggy behaviour, set "option accept-invalid-http-requests" in the relevant config section. -- Lee Garrett Tue, 31 Jan 2023 22:57:05 +0100 haproxy (1.8.0-1) experimental; urgency=medium In order to upgrade to the HAProxy 1.8 new process model, a full service restart will be performed automatically on upgrade from pre-1.8 versions when running under systemd. This incurs (minimal) service downtime and will only be performed once; future upgrades will reload haproxy seamlessly. -- Apollon Oikonomopoulos Tue, 28 Nov 2017 23:44:01 +0200 haproxy (1.4.23-1) unstable; urgency=low As of 1.4.23-1, the Debian package ships an rsyslog snippet to allow logging via /dev/log from chrooted HAProxy processes. If you are using rsyslog, you should restart rsyslog after installing this package to enable HAProxy to log via rsyslog. See /usr/share/doc/haproxy/README.Debian for more details. Also note that as of 1.4.23-1, chrooting the HAProxy process is enabled in the default Debian configuration. -- Apollon Oikonomopoulos Thu, 25 Apr 2013 23:26:35 +0300 haproxy (1.4.13-1) unstable; urgency=low Maintainer of this package has changed. -- Christo Buschek Mon, 10 Mar 2011 22:07:10 +0100 haproxy (1.3.14.2-1) unstable; urgency=low Configuration has moved to /etc/haproxy/haproxy.cfg. This allows to add the configurable /etc/haproxy/errors directory. The haproxy binary was also moved to /usr/sbin rather than /usr/bin, update your init script or reinstall the one provided with the package. -- Arnaud Cornet Mon, 21 Jan 2008 23:38:15 +0100