proxy / reverse_proxy - there is also the subdirective changes:
header_upstream / header_up etc.
transparent preset - doesn’t seem to exist so long hand via header_up
header / headers
tls > ask - doesn’t appear to be ask support (in Caddyfile V2, but mentioned in V2 config structure)
basicauth - not supported - not a big deal as I can drop those pages from serving.
root - Error during parsing: Wrong argument count with single parameter despite documentation look like the 1st parameter is optional “root [<matcher>] <path>”
Pretty sure I can script “Caddyfile v1” > “Caddyfile v2” > “Caddy v2 JSON Config” and then manipulate that to add ask functionality.
Thank you for sharing this! That’s definitely a good start to a transition guide.
Everything looks right that you said, but I’ll add comments to or clarify a few things.
You’re right, but it will have Caddyfile support soon, just need to get around to it. (Or get a contribution to speed things along)
I might be able to get this up this week.
Ah, this is a bit tricky. The documentation is right – with one nuance. A matcher token, as documented in the wiki, is of one of the three forms:
* for all requests
a request path, starting with /
match:name to specify a complex matcher by name
Since the root directive’s argument is itself a path, on Unix systems it looks like a matcher token; i.e. /var/www is indistinguishable from a matcher token. So you need root * /var/www to capture all requests and make it clear that the path is for the root path, not the request path.