Matt Holt

Yeah, thanks for working on that! No problem, we're not in a hurry :)

Is this ready to merge? If not, feel free whenever it's ready :)

I kind of like the idea of showing the corresponding JSON somehow in the Caddyfile docs. Maybe optionally expandable. (`` tag or something). Francis is right though, `caddy adapt` is...

It works on the raw bytes of the response, regardless of encoding. To manipulate the decoded body, the handler would need a way to be configured to decode the body,...

@francislavoie came up with a clever solution if the encoded content comes from `reverse_proxy`, using a subdirective: ``` header_up Accept-Encoding identity ``` (Of course, this doesn't help for precompressed static...

Is your backend compressing the response (does it support gzip compression)? If so, the replacer can't operate on compressed payloads...

Oh, you know, this is because, for efficiency reasons, we allocate the transformer chain at Provision-time instead of Request-time. So there is no `{http.request.host}` at the time the transformer chain...

That's odd. What is the output of `caddy adapt` on your config?

Huh, that's really weird. I don't have time to dig into this right now but I wanted to let you know I read your issue. If you want to dig...

Not possible at this time, but some refactoring of the handler could make it possible to use a [ResponseMatcher](https://github.com/caddyserver/caddy/blob/master/modules/caddyhttp/responsematchers.go) before employing the transformers. Want to submit a PR? (Sorry for...