Following from cloud/cloud#62 I notice that CacheControl sends the header invariably, even for error responses. I don't think this is desirable.
We need CacheControl to send the header only if the response is successful (>200, <=299)
I think it needs to hijack the ResponseWriter to accomplish this, but if there's a simpler way, do that.
Following from https://code.aneur.in/cloud/cloud/issues/62 I notice that CacheControl sends the header invariably, even for error responses. I don't think this is desirable.
We need CacheControl to send the header only if the response is successful (>200, <=299)
I think it needs to hijack the ResponseWriter to accomplish this, but if there's a simpler way, do that.
claude
was assigned by aneurin2026-09-11 10:58:22 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Following from cloud/cloud#62 I notice that CacheControl sends the header invariably, even for error responses. I don't think this is desirable.
We need CacheControl to send the header only if the response is successful (>200, <=299)
I think it needs to hijack the ResponseWriter to accomplish this, but if there's a simpler way, do that.