-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
fix: update regex for multipart content-type parsing in multipleRange #9064
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🦋 Changeset detectedLatest commit: 350adb3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Just to double check, were all permutations of Content-Type tested for this? (I'm always most cautious with electron-updater changes) |
I currently can not modify the Nginx code, so I cannot directly mock a real download scenario for testing. However, this regex has been tested against all possible return scenarios, and there were no issues. The test results are as follows.
|
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