Gallopsled/pwntools

Investigate gitlab.com caching in CI

peace-maker opened this issue · 0 comments

The proxy service in CI introduced in #2487 always shows cache misses for 404 responses of gitlab.com. I tried to have them cached too but adding the 404 http status code wasn't enough for gitlab.com apparently. Maybe some Cache control headers in the response we have to ignore?

proxy_cache_valid 200 404 12w;