56 lines
1.5 KiB
Markdown
56 lines
1.5 KiB
Markdown
---
|
|
name: Feature Request
|
|
about: Suggest a new feature or enhancement for HAProxy.
|
|
labels: 'type: feature'
|
|
---
|
|
|
|
<!--
|
|
|
|
Welcome! - We kindly ask that you:
|
|
|
|
1. Fill out the issue template below - not doing so needs a good reason.
|
|
2. Use the forum or the mailing list if you have a question rather than a bug or feature request.
|
|
|
|
The forum is at: https://discourse.haproxy.org/
|
|
|
|
The mailing list (no need to subscribe) is: haproxy@formilux.org
|
|
Subscribe to the list: haproxy+subscribe@formilux.org
|
|
Unsubscribe from the list: haproxy+unsubscribe@formilux.org
|
|
|
|
Forum and mailing list are correct places for questions about HAProxy or general suggestions
|
|
and topics, e.g. usage or documentation questions! This issue tracker is for tracking bugs and
|
|
feature requests directly relating to the development of the software itself.
|
|
|
|
Thanks for understanding, and for contributing to the project!
|
|
|
|
-->
|
|
|
|
## Output of `haproxy -vv` and `uname -a`
|
|
|
|
<!--
|
|
Please add the output of haproxy -vv you are currently using here, this helps us
|
|
later to see what has changed in HAProxy when we revisit this issue after some
|
|
time.
|
|
|
|
Put it in code blocks ```:
|
|
-->
|
|
|
|
```
|
|
(paste your output here)
|
|
```
|
|
|
|
## What should haproxy do differently? Which functionality do you think we should add?
|
|
|
|
<!--
|
|
Please describe the feature you would like us to add here.
|
|
-->
|
|
|
|
|
|
## What are you trying to do?
|
|
|
|
<!--
|
|
This section should contain a brief description what you're trying to do, which
|
|
would be possible after implementing the new feature.
|
|
-->
|
|
|