Is this Elysia or Bun bug?

I've just found a walkaround:

 async getDownload(req) {
  if (!req.params.hash || !req.params.name) return this.getIndex(req);
  const file = Bun.file(path.join(Common.settings.storage.download, req.params.hash));
  if (!await file.exists()) return this.getIndex(req);
  if (req.headers.range) {
   const chunk = Common.settings.storage.chunk_download;
   let [start = 0, end = Infinity] = req.headers.range.split('=').at(-1).split('-').map(Number);
   if (end == 0) end = start + chunk < file.size ? start + chunk : file.size;
   return new Response(file.slice(start, start + chunk), {
    status: 206,
    headers: { 'Content-Range': 'bytes ' + start + '-' + end + '/' + file.size }
   });
  } else {
   return new Response(file, {
    headers: {
     'Content-Type': 'application/octet-stream',
     'Content-Disposition': 'attachment; filename="' + req.params.name + '"'
    }
   });
  }

I've just found a walkaround:

 async getDownload(req) {
  if (!req.params.hash || !req.params.name) return this.getIndex(req);
  const file = Bun.file(path.join(Common.settings.storage.download, req.params.hash));
  if (!await file.exists()) return this.getIndex(req);
  if (req.headers.range) {
   const chunk = Common.settings.storage.chunk_download;
   let [start = 0, end = Infinity] = req.headers.range.split('=').at(-1).split('-').map(Number);
   if (end == 0) end = start + chunk < file.size ? start + chunk : file.size;
   return new Response(file.slice(start, start + chunk), {
    status: 206,
    headers: { 'Content-Range': 'bytes ' + start + '-' + end + '/' + file.size }
   });
  } else {
   return new Response(file, {
    headers: {
     'Content-Type': 'application/octet-stream',
     'Content-Disposition': 'attachment; filename="' + req.params.name + '"'
    }
   });
  }

Hmm, this walkaround seems to be working in Firefox only, not in Chrome. The problem is that the header range is present twice :(

blocked by oven-sh/bun#7051

oven-sh/bun#7051 is closed

Should have been fixed by 4ba3e85 published under 0.8.0.

Feel free to reopen the issue if the problem still persists.