This seems confusing, as there is only one matcher in my âgroupâ. Also, does the JSON process top to bottom? Can you guarantee matcher order? Assuming for my (very) limited use case I can remove the âgroupâ parameter.
This failed until I added the âgroupâ directive to both matchers in the JSON. Other wise I would rewrite, and then match the not matcher and get a 404. Shortcoming in the Caddyfile adapter? Or me not quite understand how to group things in the caddyfile? I didnât see anything in the caddyfile part of the docs about grouping.
JSON that worked. Please note I manually added the "group": "mtastsrewrite", to the not matcher grouping:
HSTS? Thatâs to let the client know I am HTTPS only, never HTTP, and how long to remember that. It is a standard header that all HTTPS sites should use.
as for /? is there a way to set the header to send out all paths? a * matcher? Iâve only ever sent that header out on /⌠I should look into the spec more.