Fix: signature calculation issue in continuous separators #476
Conversation
This file contains 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
mervinkid
added
enhancement
The signature algorithm v4 uses the decoded path without escape characters as the resource data. Signed-off-by: Mervin <[email protected]>
mervinkid
force-pushed
the
fix_sign_with_escap_character
branch
from
04b81bf to
75a45d2
Compare
leonrayang
pushed a commit
to leonrayang/cubefs
that referenced
this pull request
Feb 11, 2025
…-edit-pass Updating READMEs with Discussions tab information.
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.
What this PR does / why we need it:
The signature algorithm v4 uses the decoded path without escape characters as the resource data.
Which issue this PR fixes:
NONE.
Special notes for your reviewer:
NONE.
Release note:
NONE.