Update issue template to ask for relevant HTTP requests

This commit is contained in:
Matthew Holt 2017-03-22 18:58:57 -06:00
parent fbd6412359
commit 5341c85a27
No known key found for this signature in database
GPG Key ID: 2A349DD577D586A5

View File

@ -1,4 +1,4 @@
(Are you asking for help with using Caddy? Please use our forum instead: https://forum.caddyserver.com. If you are filing a bug report, please answer the following questions. If your issue is not a bug report, you do not need to use this template. Either way, please consider donating if we've helped you. Thanks!)
(Are you asking for help with using Caddy? Please use our forum instead: https://forum.caddyserver.com. If you are filing a bug report, please take a few minutes to carefully answer the following questions. If your issue is not a bug report, you do not need to use this template. Thanks!)
### 1. What version of Caddy are you running (`caddy -version`)?
@ -14,11 +14,17 @@
### 4. How did you run Caddy (give the full command and describe the execution environment)?
### 5. What did you expect to see?
### 5. Please paste any relevant HTTP request(s) here.
(paste curl command, or full HTTP request including headers and body, here)
### 6. What did you see instead (give full error messages and/or log)?
### 6. What did you expect to see?
### 7. How can someone who is starting from scratch reproduce this behavior as minimally as possible?
### 7. What did you see instead (give full error messages and/or log)?
### 8. How can someone who is starting from scratch reproduce the bug as minimally as possible?
(Please strip away any extra infrastructure such as containers, reverse proxies, upstream apps, dependencies, etc, to prove this is a bug in Caddy and not an external misconfiguration. Your chances of getting this bug fixed go way up the easier it is to replicate. Thank you!)