You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any known client which doesn't support Max-Age attributes ? or is this Note still really necessary for current world ?
removing this Note could urge using Expire to Max-Age (it's precedents) and will solve some problems around parsing DateTime format. and IIUC it's the motivation for adding Max-Age onto Expires
Same things happened on Cache-Control: max-age and Expires: and RFC9111 doesn't has note like this.
But if this Note still valid, developer still required to use Expires (and from point of avoid duplication, no Max-Age maybe).
The text was updated successfully, but these errors were encountered:
https://www.ietf.org/archive/id/draft-ietf-httpbis-rfc6265bis-11.html#section-4.1.2.2-3
Is there any known client which doesn't support Max-Age attributes ? or is this Note still really necessary for current world ?
removing this Note could urge using Expire to Max-Age (it's precedents) and will solve some problems around parsing DateTime format. and IIUC it's the motivation for adding Max-Age onto Expires
Same things happened on
Cache-Control: max-age
andExpires:
and RFC9111 doesn't has note like this.But if this Note still valid, developer still required to use Expires (and from point of avoid duplication, no Max-Age maybe).
The text was updated successfully, but these errors were encountered: