- 08 Jul, 2015 1 commit
-
-
Matthew Holt authored
-
- 07 Jul, 2015 1 commit
-
-
Matthew Holt authored
-
- 06 Jul, 2015 7 commits
-
-
Matt Holt authored
gzip: Const for wildcard extension (and added test)
-
Abiola Ibrahim authored
-
Abiola Ibrahim authored
-
Matthew Holt authored
-
Matthew Holt authored
-
Matthew Holt authored
-
Matt Holt authored
gzip: Make it gzip again Removes mimes filter in favor of extensions filter (might be temporary)
-
- 04 Jul, 2015 1 commit
-
-
Matthew Holt authored
-
- 03 Jul, 2015 2 commits
-
-
Matt Holt authored
preliminary test case for config/setup/markdown.go
-
Karthic Rao authored
-
- 02 Jul, 2015 2 commits
-
-
Matthew Holt authored
-
Matthew Holt authored
-
- 01 Jul, 2015 7 commits
-
-
Matthew Holt authored
-
Matt Holt authored
git: Remove from core (available as add-on)
-
Matthew Holt authored
-
Matthew Holt authored
-
Abiola Ibrahim authored
-
Matthew Holt authored
-
Matthew Holt authored
i.e. included files are also parsed as templates
-
- 30 Jun, 2015 4 commits
-
-
Abiola Ibrahim authored
-
Matt Holt authored
Massage some verbiage
-
Matt Holt authored
fastcgi: Fix for Issue 141: index not found, 502 Bad Gateway.
-
Abiola Ibrahim authored
-
- 29 Jun, 2015 2 commits
-
-
Jim Remsik authored
The grammar felt off on the sentence I changed. You can take or leave this PR, I won't be offended if you dislike my suggestion.
-
Abiola Ibrahim authored
-
- 28 Jun, 2015 2 commits
-
-
Matt Holt authored
Complete test coverage for config/setup/templates.go
-
Karthic Rao authored
-
- 27 Jun, 2015 1 commit
-
-
Abiola Ibrahim authored
Decouple git middleware from caddy core. Now available as an add-on at https://github.com/abiosoft/caddy-git.
-
- 26 Jun, 2015 4 commits
-
-
Matthew Holt authored
-
Matt Holt authored
Initial Test case for config/setup/templates.go
-
Karthic Rao authored
-
Karthic Rao authored
-
- 25 Jun, 2015 2 commits
-
-
Matthew Holt authored
-
Matt Holt authored
core: Handle address lookup and bind errors more gracefully (fixes #136 and #164)
-
- 24 Jun, 2015 4 commits
-
-
Matthew Holt authored
-
Matthew Holt authored
Addresses which fail to resolve are handled more gracefully in the two most common cases: the hostname doesn't resolve or the port is unknown (like "http" on a system that doesn't support that port name). If the hostname doesn't resolve, the host is served on the listener at host 0.0.0.0. If the port is unknown, we attempt to rewrite it as a number manually and try again.
-
Matt Holt authored
Test for webSocketParse function in config/setup
-
Karthic Rao authored
-