Skip to content

Conversation

@vrurg
Copy link
Contributor

@vrurg vrurg commented Feb 18, 2021

It is possible that a client could use invalid symbols in cookie name or
value. Cro was throwing in such situation. With this fix a cookie with
bad name or value would be skipped as if it didn't exist.

It is possible that a client could use invalid symbols in cookie name or
value. Cro was throwing in such situation. With this fix a cookie with
bad name or value would be skipped as if it didn't exist.
FCO pushed a commit to FCO/cro-http that referenced this pull request Oct 2, 2025
FCO pushed a commit to FCO/cro-http that referenced this pull request Oct 2, 2025
japhb added a commit that referenced this pull request Oct 2, 2025
Fix throwing with client-supplied invalid cookie (copy of #126 vrurg++)
@japhb
Copy link
Contributor

japhb commented Oct 2, 2025

Closed in favor of #210 which is an updated copy of this one.

@japhb japhb closed this Oct 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants