Skip to content

Conversation

@bagder
Copy link
Member

@bagder bagder commented Apr 4, 2023

Meaning that it would wrongly still store the fragment using spaces instead of %20 if allowing space while also asking for URL encoding.

Discovered when playing with trurl.

Added test to lib1560 to verify the fix.

Meaning that it would wrongly still store the fragment using spaces
instead of %20 if allowing space while also asking for URL encoding.

Discovered when playing with trurl.

Added test to lib1560 to verify the fix.
@github-actions github-actions bot added the tests label Apr 4, 2023
@bagder bagder closed this in f042e1e Apr 5, 2023
@bagder bagder deleted the bagder/url-fragment-urlencode branch April 5, 2023 06:30
bch pushed a commit to bch/curl that referenced this pull request Jul 19, 2023
Meaning that it would wrongly still store the fragment using spaces
instead of %20 if allowing space while also asking for URL encoding.

Discovered when playing with trurl.

Added test to lib1560 to verify the fix.

Closes curl#10887
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

1 participant