Cutlery/caddy
1
0
Fork 0
mirror of https://github.com/caddyserver/caddy.git synced 2025-06-23 15:31:40 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updated Caddyfile (markdown)

Matt Holt 2015-01-21 19:45:31 -07:00
parent d06eea78b4
commit 8702b5154e
1 changed files with 3 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
Caddyfile.md

@ -34,9 +34,8 @@ mydomain.com:80 {
redirect / :443 301 redirect / :443 301
} }
# Curly braces can be on their own line if you prefer # Curly braces must open at the end of a line
mydomain.com:443 mydomain.com:443 {
{
gzip gzip
ext .html .htm ext .html .htm
tls cert.pem key.pem tls cert.pem key.pem
@ -49,6 +48,4 @@ In the above file, the keywords `redirect`, `gzip`, `ext`, and `tls` are directi
To learn about what directives are available, please see the list of directives in this wiki. To learn about what directives are available, please see the list of directives in this wiki.
As you can tell, whitespace separates different arguments/parameters. You can group multiple words into a single argument by enclosing it "in quotes". As you can tell, whitespace separates different arguments/parameters. You can group multiple words into a single argument by enclosing it "in quotes".
For those who want to check their understanding: the file above serves `mydomain.com` on ports 80 and 443 (the HTTP and HTTPS ports). All requests to port 80 are redirected to 443, the secure port, with a 301 status code. All requests to port 443 are gzipped. Then, if an extension was not added to the URL, the .html extension will be internally added if the resource exists (and if not, it tries .htm). In other words, it serves clean, extensionless URLs by inferring the file extension. The tls line enables TLS using the certificate and key files listed.