33 lines
1 KiB
Markdown
33 lines
1 KiB
Markdown
|
<!--
|
|||
|
|
DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS.
|
|||
|
|
|
|||
|
|
The issue tracker is for reporting bugs and feature requests only.
|
|||
|
|
For end-user related support questions, refer to one of the following:
|
|||
|
|
|
|||
|
|
- Stack Overflow (using the "traefik" tag): https://stackoverflow.com/questions/tagged/traefik
|
|||
|
|
- the Traefik community Slack channel: https://traefik.herokuapp.com
|
|||
|
|
|
|||
|
|
-->
|
|||
|
|
|
|||
|
|
|
|||
|
|
### Do you want to request a *feature* or report a *bug*?
|
|||
|
|
|
|||
|
|
Feature
|
|||
|
|
|
|||
|
|
### What did you expect to see?
|
|||
|
|
|
|||
|
|
<!--
|
|||
|
|
|
|||
|
|
HOW TO WRITE A GOOD ISSUE?
|
|||
|
|
|
|||
|
|
- Respect the issue template as much as possible.
|
|||
|
|
- If it's possible use the command `traefik bug`. See https://www.youtube.com/watch?v=Lyz62L8m93I.
|
|||
|
|
- The title must be short and descriptive.
|
|||
|
|
- Explain the conditions which led you to write this issue: the context.
|
|||
|
|
- The context should lead to something, an idea or a problem that you’re facing.
|
|||
|
|
- Remain clear and concise.
|
|||
|
|
- Format your messages to help the reader focus on what matters and understand the structure of your message, use Markdown syntax https://help.github.com/articles/github-flavored-markdown
|
|||
|
|
|
|||
|
|
-->
|
|||
|
|
|