JeDaYoshi

Seriously considering deprecating this, but I want to leave support for those who don't want to do WebRTC, but this doesn't works properly unless something fun is done.

It's honestly the right thing. Streaming MPEG1 via a TLS connection is not the best thing and hasn't been since a start. I suppose that, unless it is changed how...

This seems to happen randomly. It worked for me after ~3-4 tries, unsure of what's wrong and whether it's something specific of `node-gyp` or something with `nodejs.org` itself not liking...

> If I have hostX.serviceA.domain.tld, hostY.serviceA.domain.tld, hostX.serviceB.domain.tld, hostY.serviceB.domain.tld, then all of those would be covered by the \*.\*.domain.tld certificate (does ACME even allow such certificates? 🤔). @abjugard `*.domain.tld` won't cover...

@mholt Most warnings that REDbot reported as shown in here have been fixed (checked just now), except for the "Vary" one. "Vary" header is still not being sent for requests...

Actually, nevermind - it still gives a warn when "If-None-Match" is used: 

> About your question, IMO the fix should be that 304 keeps the same `Vary` 200 would produce. The `ETag` one I'm not exactly sure. I'm not sure about the...

@mholt Both issues are present. My screenshots are on the latest commit @ master. The issue with Vary I already mentioned it [in this comment](https://github.com/caddyserver/caddy/issues/5849#issuecomment-2063904233). It is different to the...

I'm not testing locally. I am using [the hosted instance](https://redbot.org) against a Caddy instance on a VPS.

Seems like adding a `header Vary "XXX"` will add two separate Vary headers instead of merging them together, whether it's a `header Vary "Accept-Encoding"` or any other value. However, the...