b1285d5ce0
* the time-out fix introduced in 1.1.25 caused a corner case where it was possible for a client to keep a connection maintained regardless of the timeout if the server closed the connection during the HEADER phase, while the client ignored the close request while doing nothing in the other direction. This has been fixed now by ensuring that read timeouts are re-armed when switching to any SHUTW state. * enhanced error reporting in the logs. Now the proxy will precisely detect various error conditions related to the system and/or process limits, and generate LOG_EMERG logs indicating that a resource has been exhausted. * logs will contain two new characters for the error cause : 'R' indicates a resource exhausted, and 'I' indicates an internal error, though this one should never happen. * server connection timeouts can now be reported in the logs (sC), as well as connections refused because of maxconn limitations (PC). * new global configuration keyword "ulimit-n" may be used to raise the FD limit to usable values. * a warning is now displayed on startup if the FD limit is lower than the configured maximum number of sockets. * new configuration keyword "monitor-net" makes it possible to be monitored by external devices which connect to the proxy without being logged nor forwarded to any server. Particularly useful on generic TCPv4 relays. |
||
|---|---|---|
| .. | ||
| build.cfg | ||
| config.rc.haproxy | ||
| debug2ansi | ||
| debug2html | ||
| debugfind | ||
| examples.cfg | ||
| haproxy-1.1.21-flx.1.pkg | ||
| haproxy.cfg | ||
| haproxy.init | ||
| haproxy.spec | ||
| init.haproxy | ||
| init.haproxy.flx0 | ||
| rc.highsock | ||