Parse set header cookies properly #5084
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.
Description
Currently when an empty cookie attribute (
Secure
,HttpOnly
...) is encountered while parsing aSet-Cookie
header it will create aCookieAttrs
object containing a (key, value) pair with an empty string for the attribute value ie:Resulting in an updated
Set-Cookie
header for theResponse
object with invalid values for those empty attributes ie:My browser (Firefox 95.0.1) does not pickup these attributes so the cookie looses them.
This fix replaces the empty string attribute for empty cookie attributes by the value
None
ie:So that they can be told apart from attributes with intentional empty string values when setting the updated header, which results in a properly formatted header:
Checklist