Fix issue of blob batch request handling error when boundary includes '=' #2421
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.
JS storage SDK doesn't use boundary with '='. Cannot easily implement a test case to generate request with boundary with '='.
Manually tested the change with cases like:
Storage service response looks like:
Content-Type: multipart/mixed; boundary=batch==d88eec8e-68ce-450a-b029-b6e3072638d5; boundary=1111
Storage service response looks like:
Azurite response looks like:
Storage service response looks like:
Azurite response looks like: