Fix handling of multiple double dots above root in parsing of relative URI #752
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
|
Thanks! I'll release Gatling 2.0.2 on monday with this fix! |
slandelle
pushed a commit
that referenced
this pull request
Oct 31, 2014
Fix handling of multiple double dots above root in parsing of relative URI, close #751
|
Great! Looking forward to new Gatling release. |
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.
Attempt to fix #751.
I encountered this error through usage of Gatling on a page which in some cases produced resource URLs like the ones mentioned in the issue. Although one may argue that such URLs should not be present on a page, it poses a problem in that Gatling just appears to hang (when AHC enters its infinite loop).
Due to its usage in Gatling, I think this fix should probably be merged to the 1.9.x branch as well.