Matt Holt

Is this strictly true for all SPAs? Mine work without this. The example here should be as minimal as possible, but in the new docs we can expand the examples.

Oh I haven't got them ready yet. 😅 that's on me, I'm a bit behind lately.

The client to a forward proxy (Caddy A in your example) needs to support forward proxies. I believe the HTTP(S)_PROXY env var(s) can do this, but I haven't played with...

Oh actually we have a setting for this in the reverse_proxy: https://caddyserver.com/docs/modules/http.reverse_proxy.transport.http#forward_proxy_url or Caddyfile: https://caddyserver.com/docs/caddyfile/directives/reverse_proxy#forward_proxy_url

You might be able to do it with the [`request_header` directive](https://caddyserver.com/docs/caddyfile/directives/request_header)?

@sigmavirus24 Actually, I can probably close this issue. The draft ARI spec changed last-minute and no longer uses OCSP-esque CertIDs, so it's no longer a need I have. If others...

> I hear what you're saying here, but somehow handle_errors works fine when the encode directive is removed. The `encode` directive wraps the response writer, so if a response starts...

> Maybe @dunglas or @mholt have the answer ? Sorry, I've looked at the linked issues but I'm not sure I understand what the question is exactly ("how Caddy merges...

@7-zete-7 Weird, I cannot reproduce the error with that config. It adapts to this JSON and seems to work fine: ```json { "apps": { "http": { "servers": { "srv0": {...

@7-zete-7 Ah, gotcha. Well, kind of: > this information does not make it clear that the configurations will be merged What do you mean by "the configurations will be merged"?...