This repository was archived by the owner on May 5, 2020. It is now read-only.
Fix fragment caching in mixed encoding scenario - #39
Merged
Conversation
To reduce ambiguity between char- and byte-based operations, explicitly do byte operations when extracting the fragment that needs to be cached.
tmm1
added a commit
that referenced
this pull request
Jan 9, 2014
Fix fragment caching in mixed encoding scenario
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Fixes the case where a fragment cache might get persisted with a few extra bytes of garbage due to
String#lengthmeaning different things in different encodings.