A better fix for #1894 - "Undefined offset: 0" #1998
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.
There's a bug in
SetCookie::fromString()
which throws an "Undefined offset: 0" error if the inputted$cookie
string is missing its first key-value pair, but has at least one other pair. For example, it would be triggered with the following (malformed) cookie:Another author submitted a pull request for this (#1894), but the request was rejected due to improper test writing. However, I don't believe the fix itself is appropriate, as I documented there.
So I am submitting my own pull request. The change is trivial. It makes the function return an empty cookie in response to this input, which is the same behavior as this function already has when the first key-value pair is missing the cookie name.