Open Bug 1416976 Opened 8 years ago Updated 3 years ago

WAV files show as ridiculously long when content length headers are missing

Categories

(Core :: Audio/Video: Playback, defect, P3)

59 Branch
defect

Tracking

()

UNCONFIRMED

People

(Reporter: doomtay, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0 Build ID: 20171113100232 Steps to reproduce: Open a page in Wayback Machine containing WAV audio (https://asciiexpress.net/gameserver/bc's_quest_for_tires.html) Actual results: Audio controls showed a long duration time. When the sound is played to the end or seeked past the real sound duration, the seek bar snaps to the end Expected results: The audio control bar should display the real duration Attached is a simpler example. Left is from the original source, and right is from Wayback Machine, which does not include a content length header
(In reply to doomtay from comment #0) > Attached is a simpler example. Left is from the original source, and right > is from Wayback Machine, which does not include a content length header Why is this not considered to be a bug in the Wayback Machine?
I cobbled together a local server in NodeJS, and explicitly set it to not serve a content length, and the issue (sometimes) manifests there too
With a cache buster and no content length header, the issue always manifests

This also happens with wav files encoded as data urls

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: