Hello! Thanks for the contribution.

It looks like the tests are running, but Caddy is interfering; if you hover over the first blue question mark circle in the caddy column, it says: "PUT config resulted in 200 OK", which indicates that the config response status code is being changed (it should be a 201 Created).

You can dig into this by running the test on its own:

./test-docker.sh -i freshness-none caddy

... which should show you a detailed trace of the requests and responses, both from the client and server's standpoints.

I suspect what's happening is that Caddy is somehow defaulting to blocking or not properly handling PUT requests when being used as a reverse proxy.

Hi ! Sorry, I have been a bit busy. I did see indeed that some tests were not working as intended, I'll try to look into it asap :)
@darkweak, pinging you just in case you would like to have a look at some point :)

Commenting again just to confirm that it must be an issue(?) with Caddy transforming the response status code from 201 to 200 (while keeping the response body as is). It seems to also apply for other HTTP methods. For instance, trying to call

GET http://localhost:8006/config/SOME_UUID

(with 8006 being caddy port, proxying to Node on 8000), should return a 405 (cf handle-config.mjs), but also returns a 200.

I'll try to setup a simple reproducer to catch what might be wrong (or badly setup from my part)

PS: I read about no-op requests for Caddy (https://caddy.community/t/why-caddy-emits-empty-200-ok-responses-by-default/17634), but it does not seem to be our case here

I will check that too @JacquesDurand

@mnot I don't understand why it keeps getting gray circle for some cateogries (e.g. Cache-Control freshness category) but works for others.

Edit: I didn't read the icon description at the bottom.

I've got it working with caddy + cache-handler; see the notes.