Merge Expires and Max-Age attributes #33369
Closed
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.
org.springframework.http.client.reactive.ClientHttpResponse
and its implementations don't processExpires
Cookie attribute. However, they only processMax-Age
attribute.Logic defined in RFC 6265. Point 3 of section 5.3 in this RFC gives higher precedence to
Max-Age
overExpires
. This change follows this RFC and does the following:1- If both
Max-Age
andExpires
attribute are present in the cookie, setmaxAge
field inResponseCookie
toMax-Age
attribute.2- If only
Expires
attribute is present in the cookie, setmaxAge
field inResponseCookie
toExpires
attribute.2- If only
Max-Age
attribute is present in the cookie, setmaxAge
field inResponseCookie
toMax-Age
attribute.Closes #33157