Bug: Duplicate header "Content-Range" in Response (cannot play html video)

[libersoft-org]

What version of Bun is running?

1.0.11

What platform is your computer?

Linux 6.1.0-13-amd64 x86_64 unknown (Debain 12)

What steps can reproduce the bug?

const chunk = 1048576; // 1 MB
let [start = 0, end = Infinity] = req.headers.range.split('=').at(-1).split('-').map(Number);
if (end == 0) end = start + chunk < file.size ? start + chunk - 1 : file.size - 1;
const file = Bun.file('big_video.mp4');
return new Response(file.slice(start, start + chunk), {
 status: 206,
 headers: { 'Content-Range': 'bytes ' + start + '-' + end + '/' + file.size }
});

What is the expected behavior?

To have a single header "Content-Range" in response.

What do you see instead?

Two "Content-Range" headers in response.

Additional information

This is because bun does not know the file size, so it creates "Content-Range" ending "/*" instead of "/file_size". So it ends up like this in response:

content-range: bytes 30269309-31317884/1063300891
content-range: bytes 30269309-31317884/*

... two headers "content-range" instead of just one that I set in response.

This is quite a problem when playing a video in "video" html element, because it doesn't know the size of the video, so I have to wait when the whole file is downloaded. Considering video files can have 1 GB+, this is a problem.

Firefox is OK with those two headers and plays the video well, but Chrome does not.

[TomasHubelbauer]

@libersoft-org Thank you for including the video streaming sample code. I was looking for something exactly like this and came across this issue while googling around. You've saved me a bunch of time.

[libersoft-org]

@libersoft-org Thank you for including the video streaming sample code. I was looking for something exactly like this and came across this issue while googling around. You've saved me a bunch of time.

You're welcome!