Details
-
Improvement
-
Status: Open
-
Trivial
-
Resolution: Unresolved
-
None
-
None
-
Security Level: Public (Anyone can view this level - this is the default.)
-
None
Description
current haproxy configuration when using Load-Balancing in a VPC scenario contain hardcoded timeout parameter that could be define by the user:
current default values:
timeout connect 5000 timeout client 50000 timeout server 50000
would be intereinst to support change of them via the API when creating load-balancing.
Attachments
Issue Links
- is related to
-
CLOUDSTACK-9546 X-Forwarded-For Headers Not Applied for HTTP Traffic in haproxy
- Open