Browse Source
In the Caddyfile, hosts specified for HTTP sockets (either scheme is "http" or it is on the HTTP port) should not be used as subjects in TLS automation policies (APs).master
Matthew Holt
4 years ago
3 changed files with 90 additions and 1 deletions
@ -0,0 +1,68 @@ |
|||
# (this Caddyfile is contrived, but based on issues #4176 and #4198) |
|||
|
|||
http://example.com { |
|||
} |
|||
|
|||
https://example.com { |
|||
tls internal |
|||
} |
|||
|
|||
---------- |
|||
{ |
|||
"apps": { |
|||
"http": { |
|||
"servers": { |
|||
"srv0": { |
|||
"listen": [ |
|||
":443" |
|||
], |
|||
"routes": [ |
|||
{ |
|||
"match": [ |
|||
{ |
|||
"host": [ |
|||
"example.com" |
|||
] |
|||
} |
|||
], |
|||
"terminal": true |
|||
} |
|||
] |
|||
}, |
|||
"srv1": { |
|||
"listen": [ |
|||
":80" |
|||
], |
|||
"routes": [ |
|||
{ |
|||
"match": [ |
|||
{ |
|||
"host": [ |
|||
"example.com" |
|||
] |
|||
} |
|||
], |
|||
"terminal": true |
|||
} |
|||
] |
|||
} |
|||
} |
|||
}, |
|||
"tls": { |
|||
"automation": { |
|||
"policies": [ |
|||
{ |
|||
"subjects": [ |
|||
"example.com" |
|||
], |
|||
"issuers": [ |
|||
{ |
|||
"module": "internal" |
|||
} |
|||
] |
|||
} |
|||
] |
|||
} |
|||
} |
|||
} |
|||
} |
Loading…
Reference in new issue