node: Use hash based cache path in FilesystemBasedCache#515
Merged
Conversation
FilesystemBasedCache previously used an escaped version of the full cache key as the filename. Since cache keys include full URLs, this could exceed the 255-byte filename limit. So use SHA256 based cache path. For backward compatibility, legacy cache entries are migrated to the new cache path. Fixes #443
bbhtt
force-pushed
the
bbhtt/node-fix-cache-filename
branch
from
8e6febb to
7fe4755
Compare
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
FilesystemBasedCache previously used an escaped version of the full cache key as the filename. Since cache keys include full URLs, this could exceed the 255-byte filename limit. So use SHA256 based cache path. For backward compatibility, legacy cache entries are migrated to the new cache path.
Fixes #443