mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2024-12-27 07:02:11 +00:00
3ba77d29ac
For 6 years now we've been seeing a warning suggesting to set dh-param beyond 1024 if possible when it was not set. It's about time to do it and get rid of this warning since most users seem to already use 2048. It will remain possible to set a lower value of course, so only those who were experiencing the warning and were relying on the default value may notice a change (higher CPU usage). For more context, please refer to this thread : https://www.mail-archive.com/haproxy@formilux.org/msg37226.html This commit removes a big chunk of code which happened to be needed exclusively to figure if it was required to emit a warning or not :-) |
||
|---|---|---|
| .. | ||
| design-thoughts | ||
| internals | ||
| lua-api | ||
| 51Degrees-device-detection.txt | ||
| acl.fig | ||
| architecture.txt | ||
| close-options.txt | ||
| coding-style.txt | ||
| configuration.txt | ||
| cookie-options.txt | ||
| DeviceAtlas-device-detection.txt | ||
| gpl.txt | ||
| haproxy.1 | ||
| intro.txt | ||
| lgpl.txt | ||
| linux-syn-cookies.txt | ||
| lua.txt | ||
| management.txt | ||
| netscaler-client-ip-insertion-protocol.txt | ||
| network-namespaces.txt | ||
| peers-v2.0.txt | ||
| peers.txt | ||
| proxy-protocol.txt | ||
| queuing.fig | ||
| regression-testing.txt | ||
| seamless_reload.txt | ||
| SOCKS4.protocol.txt | ||
| SPOE.txt | ||
| WURFL-device-detection.txt | ||