Matt Holt

@mheyman To clarify, ***all*** replacements are processed at config load (startup), not at every request, whether using regular expressions or not: https://github.com/caddyserver/replace-response/blob/9d5652c0256308fddaef1453d463d2a281498cb6/handler.go#L88-L99 Unless there's a clever solution I haven't thought...

I guess that's technically possible, but it adds a lot of complexity.

This is a known issue when traversing the JSON structure. When looking up module docs directly, we can handle it properly: - https://caddyserver.com/docs/modules/caddy.storage.consul - https://caddyserver.com/docs/modules/caddy.storage.s3 You can see how both...

Basically, just post your Caddy configs you're already using and we'll take it from there. It would be nice if you comment parts that aren't obvious, or which are optional,...

@mustafa0x Thanks for that search, I dunno how useful a pile of 7K of them will be, but maybe I can scan those and look for some common patterns that...

@dbaynard Thanks, there's some good content there. @randomairborne Which one, exactly?

Yes, true -- as I said above, most websites don't like that kind of proxying, so we'd have to make a note of it. I like the distinction between templated...

> but `caddy reload` does not accept the `--envfile` flag. We could probably change that. I don't think it would be able to _reset_ the environment but we could at...

Yeah, I'd like to see more info on JSON docs too, but haven't really had time. For now, we do have a quick ["Writing a Caddy JSON config from scratch"...

@phish108 > the docs are misleading in this case because they state that no rewrite takes place Where does it say that? In fact, the `uri` and `handle_path` directives are...