Is there caching of reverse_proxy? (stuck song names on internet radio)

[severak]

1. Output of caddy version:

v2.5.1 h1:bAWwslD1jNeCzDa+jDCNwb8M3UJ2tPa8UZFFzPVmGKs=

2. How I run Caddy:

via Debian systemd, this works without problems

d. My complete Caddy config:

(this is only excerpt relevant to my problem, not a full config)

http://radio.example.org, https://radio.example.org {
        reverse_proxy http://localhost:8000
}

I serve both HTTP and HTTPS because

3. The problem I’m having:

I have private internet radio (hence I redacted domain names) powered by Icecast 2 behing Caddy proxy (for HTTPS and additional security).

The problem is that song names are not updated. These are served at /status-json.xsl route by Icecast.

I am not sure if this is somewhat being cached by Caddy or if this is some mishap on Icecast side. If this is cached by Caddy, how do I disable cache? I found out flush_interval settings in docs, but I am not sure if “The proxy buffers responses by default for wire efficiency” means that responses are being cached.

5. What I already tried:

forcing Icecast to update song name manually, this worked sometimes

6. Links to relevant resources:

• reverse_proxy (Caddyfile directive) — Caddy Documentation

[matt (Matt Holt)]

Buffering is different from caching.

(And we’re clarifying those docs for the 2.6 release soon.)

The proxy does not do any caching. It does do connection pooling, but the transport implementation is irrelevant for the semantics of HTTP requests, which are stateless.

In order for us to help you more, you’ll need to fill out the help template completely. Unfortunately parts of it are totally missing, and there’s no way for us to verify or recreate the behavior you’re describing.