fix: update regex for multipart content-type parsing in multipleRange #9064
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.
The

Content-Type
response is as follows:Content-Type: multipart/byteranges; boundary=799ddd5a-943e-4e22-981d-e32596ca39d2
. Theboundary
can have a space before it or no space at all.Here's the rfc:
https://datatracker.ietf.org/doc/html/rfc7231#section-3.1.1.1
Issue
Currently, the check only accounts for cases where there is a space. If some servers return a response without a space, it will cause incremental downloads to fail.
Error Info
How to fix
might fix #9063