fix: Include expires header on 304 cache hit #438
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When configured with a TTL, the relay proxy will include an
expires
header when a flag or segment is first requested. This informs the PHP SDK how long it can cache the response.Once the SDK makes another request, it is possible the flag still hasn't changed. In that situation, we should return a new
expires
header. Otherwise, the PHP SDK will have no idea how long it should cache this new response for, resulting in it re-fetching on demand going forward.