Cached responses always have a 200 status code

[bertday]

If you hit an endpoint with caching enabled, the first response will have the same status code as the underlying API response. Any requests after that will return 200, even if the original response was an error.

[themightychris]

Good catch, did the original 404 response include cache control headers? I wonder if non-200 responses should have any special handling applied on top of the underlying cache-control headers from the upstream API

[bertday]

@themightychris the only control header on the upstream response was max-age=3600. Is there a best practice around that we should be using (i.e. that will change the behavior in Gatekeeper)?

[themightychris]

@rbrtmrtn Gatekeeper caches according to upstream caching headers. Best practice on what those should be for non-200 responses is debatable. It seems reasonable that 404s should be cached the same as 200s, but anything else is less obvious