Use rfc2396 parser instead of URI::DEFAULT_PARSER
#139
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hsbt
force-pushed
the
use-rfc2396-parser
branch
from
53f79f8 to
0cf6b84
Compare
dentarg
approved these changes
Aug 8, 2024
dentarg
changed the title
URI::DEFAULT_PARSER
|
Released in v3.0.2 |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixed up #138
URI::DEFAULT_PARSER.escapeis obsoleted at next stable release of URI. We should useURI::RFC2396_PARSER.escapeinstead ofURI::DEFAULT_PARSER.