RFC8246 HTTP Immutable Responses#462
Conversation
|
|
||
| // calculate freshness lifetime | ||
| final Duration freshnessLifetime = calculateFreshnessLifetime(cacheControl, response); | ||
|
|
There was a problem hiding this comment.
@arturobernalg I cannot find immutable cache control directive mentioned anywhere in the RFC 9111. Am I missing something?
@arturobernalg Could you please reflect this in the PR title and the commit message? |
@ok2c |
|
@arturobernalg Looks good to me, but can we drop |
This commit adds the functionality to handle the 'immutable' directive in the Cache-Control header as per the RFC8246 specifications. Key changes include: - The 'immutable' directive is checked in the Cache-Control of an HTTP response, indicating that the origin server will not update the resource representation during the response's freshness lifetime. - If the 'immutable' directive is present and the response is still fresh, the response is considered cacheable without further validation. - Ignoring any arguments with the 'immutable' directive, as per RFC stipulations. - Treating multiple instances of the 'immutable' directive as equivalent to one.
@ok2c Removed. |
This commit adds the functionality to handle the 'immutable' directive in the Cache-Control header as per the RFC8246 specifications. Key changes include: - The 'immutable' directive is checked in the Cache-Control of an HTTP response, indicating that the origin server will not update the resource representation during the response's freshness lifetime. - If the 'immutable' directive is present and the response is still fresh, the response is considered cacheable without further validation. - Ignoring any arguments with the 'immutable' directive, as per RFC stipulations. - Treating multiple instances of the 'immutable' directive as equivalent to one.
This commit adds the functionality to handle the 'immutable' directive in the Cache-Control header as per the RFC8246 specifications. Key changes include: - The 'immutable' directive is checked in the Cache-Control of an HTTP response, indicating that the origin server will not update the resource representation during the response's freshness lifetime. - If the 'immutable' directive is present and the response is still fresh, the response is considered cacheable without further validation. - Ignoring any arguments with the 'immutable' directive, as per RFC stipulations. - Treating multiple instances of the 'immutable' directive as equivalent to one.
This commit adds the functionality to handle the 'immutable' directive in the Cache-Control header as per the RFC specifications.
Key changes include: