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
[Bug]: No range with registerStreamProtocol #30924
Comments
I have the same problem when I use |
@vbourgeois, could you provide a minimal reproduce case for this? Also, are you registering |
Seems this is still an issue. Range headers don't work. BTW I am using both Is there any workarounds for this or plans to fix? If there's bandwidth to look into it, I'm sure I could create a minimal reproduction in a repo. |
I don't have a lot of time to provide a reproduce case now. I'll try to do it in few days if I can.
Yes and it didn't resolve the issue.
I'm using an express server to stream video & sound in Electron now. |
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment! |
This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue on a supported version of Electron please open a new issue and include instructions for reproducing the issue. |
Preflight Checklist
Electron Version
14.0.0
What operating system are you using?
Other Linux
Operating System Version
Mint 19.3
What arch are you using?
x64
Last Known Working Electron version
6.1.12
Expected Behavior
Hello,
I have registered a custom protocol with registerStreamProtocol in order to read offline audios and videos in my app. When I'm trying to "navigate" through the video I'm expecting to receive a range header in order to properly read the video stream with nodejs.
Actual Behavior
But I'm not receiving any range header in the request...
Here is an example of the issue :
Here is what I'm receiving in the request :
=>
lls-encrypted-stream://
is my custom protocol and you can see that the range is not properly set.Last time it was working correctly was in electron 6.x
You can see the historic of the bug in this issue : #21018
Testcase Gist URL
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: