-
Notifications
You must be signed in to change notification settings - Fork 836
Insights: haproxy/haproxy
Overview
-
0 Active pull requests
-
- 0 Merged pull requests
- 0 Open pull requests
- 4 Closed issues
- 6 New issues
Could not load contribution data
Please try again later
4 Issues closed by 4 people
-
3.2-dev14: ssl-f-use does not work well with the 'bind strict-sni' option
#2966 closed
May 9, 2025 -
tune.lua.bool-sample-conversion normal has no effect to warning emitted by HAproxy 3.2-dev13
#2957 closed
May 9, 2025 -
FastCGI connection reuse leads to stuck backend connections
#2936 closed
May 6, 2025 -
Better parseable dumps/traces
#2960 closed
May 6, 2025
6 Issues opened by 5 people
-
send-proxy-v2 in Rings results in segfault
#2965 opened
May 7, 2025 -
Stateless, nonceless encryption & decryption API
#2964 opened
May 6, 2025 -
send-proxy should not use IPv6 mapped IPv4 addresses
#2963 opened
May 6, 2025 -
stick-tables and IPv6 improvements needed
#2962 opened
May 6, 2025 -
Expose statistics relating to log forwarding and ring buffers
#2961 opened
May 5, 2025 -
3.2-dev14: Segfault in stick_tables
#2959 opened
May 5, 2025
6 Unresolved conversations
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
Haproxy randomly returns 502 Bad Gateway
#2368 commented on
May 4, 2025 • 0 new comments -
WDT/Hang on check_user crypt_r 3.1.7
#2956 commented on
May 5, 2025 • 0 new comments -
Quoted empty string in config file treated as terminator
#2944 commented on
May 5, 2025 • 0 new comments -
JA4 support in haproxy
#2495 commented on
May 6, 2025 • 0 new comments -
Can OpenSSL 3.5 replace quictls when building Haproxy with USE_QUIC=1 USE_OPENSSL=1?
#2948 commented on
May 7, 2025 • 0 new comments -
Feature Request: builtin ACME client support
#1864 commented on
May 11, 2025 • 0 new comments