1735014 - Content-Type audio/x-mpegurl recognised as application/vnd.apple.mpegurl

Status: NEW

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

Description

[marko.bozikovic]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:93.0) Gecko/20100101 Firefox/93.0

Steps to reproduce:

Firefox 93 on Windows 10 Pro.

I run TvHEadend server (HTS Tvheadend 4.3-1947). To watch TV on my computer, I open its web UI, go to EPG tab, click on programme info and then the "Play" button.

Firefox then opens its "Opening" dialogue, I'd select "Open with" ... MPC-HC (Media Player Classic) from the dropdown and it would open and play the stream.

I've upgraded Firefox from 91.x to 93. MPC and TVheadend have not been upgraded.

TVheadend version is HTS Tvheadend 4.3-1947~gdbaa0f850 (running linuxserver/tvheadend image on RPi4).

MPC-HC is version 1.9.16, 2021/09/22 build.

Actual results:

As of Firefox 93 (I upgraded from 91.x), the "Opening" dialogue no longer offers a dropdown menu. When I click "Browse" and select MPC, MPC claims it cannot render the file.

The stream URL has no file extension, but Content-Type is audio/x-mpegurl (checked using Developer tools). I've noticed that the "Opening" dialogue claims the type of the URL is application/vnd.apple.mpegurl.

If I save the file and give it .m3u extension, MPC opens and plays it correctly.

Expected results:

"Opening" dialogue should offer MPC in the dropdown and MPC should play the stream.

Comment 1

[marko.bozikovic]

I've attached screenshots from Firefox 92 and 93, when opening the same stream on the same TVheadend server.

Comment 2

[marko.bozikovic]

Attachment: pitv-open-stream-ff92.png

FF92 opening TVheadend stream

Comment 3

[marko.bozikovic]

Attachment: pitv-open-stream-ff93.png

FF 93 opening the TVheadend stream

Comment 4

[marko.bozikovic]

Attachment: pitv-open-stream-headers-FF92.png

FF 92 headers

Comment 5

[marko.bozikovic]

Attachment: pitv-open-stream-headers-FF93.png

FF 93 headers

Comment 6

[Timea Cernea [:tbabos][inactive]]

Hi marko,
Could you please also provide a site from where such file types can be downloaded?

Comment 7

[marko.bozikovic]

Not directly, sorry. This is my local TVHeadEnd server. You'd need a Linux server with a DVB-T/C/S capture card and set up an instance of TVHeadEnd.

I could send you raw response header and body, so you could try emulating the response?

Comment 8

[Marco Bonardo [:mak] (Away 10-21 August)]

What would really help us here, is to understand when the problem started.
To help us with that, could you please run a mozregression? See https://mozilla.github.io/mozregression/ for instructions, the whole process is partially automated and in the end it will give you a link to our repository, that we can use to tell exactly which change caused the problem.
Since this requires a specific setup, it's probably easier to do this way.
That way we can largely speed up the debugging of the issue.

Comment 9

[marko.bozikovic]

Hi,

Sorry for a late reply, was a busy week :-) Here's the result:

app_name: firefox
build_date: 2021-08-11 13:14:17.369000
build_file: C:\Users\temp\.mozilla\mozregression\persist\6d5e0e27fc50-shippable--autoland--target.zip
build_type: integration
build_url: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/cCLt4lvxT0OE2RhYGYSMlg/runs/0/artifacts/public%2Fbuild%2Ftarget.zip
changeset: 6d5e0e27fc50caf1cababdce042a73396027ae2d
pushlog_url: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=a1a26ba25fbc5ffcfe850e7ead9eada89cfdfa7e&tochange=6d5e0e27fc50caf1cababdce042a73396027ae2d
repo_name: autoland
repo_url: https://hg.mozilla.org/integration/autoland
task_id: cCLt4lvxT0OE2RhYGYSMlg

The last few lines of the log:

2021-10-25T20:15:58.785000: INFO : Narrowed integration regression window from [25297aea, ffba9897] (4 builds) to [30011f52, ffba9897] (2 builds) (~1 steps left)
2021-10-25T20:15:58.795000: DEBUG : Starting merge handling...
2021-10-25T20:15:58.795000: DEBUG : Using url: https://hg.mozilla.org/integration/autoland/json-pushes?changeset=ffba9897b9eb24e7722de9c556ad58de094dffa2&full=1
2021-10-25T20:15:58.795000: DEBUG : redo: attempt 1/3
2021-10-25T20:15:58.796000: DEBUG : redo: retry: calling _default_get with args: ('https://hg.mozilla.org/integration/autoland/json-pushes?changeset=ffba9897b9eb24e7722de9c556ad58de094dffa2&full=1',), kwargs: {}, attempt #1
2021-10-25T20:15:58.799000: DEBUG : urllib3.connectionpool: Resetting dropped connection: hg.mozilla.org
2021-10-25T20:16:00.150000: DEBUG : urllib3.connectionpool: https://hg.mozilla.org:443 "GET /integration/autoland/json-pushes?changeset=ffba9897b9eb24e7722de9c556ad58de094dffa2&full=1 HTTP/1.1" 200 None
2021-10-25T20:16:00.188000: DEBUG : Found commit message:
Bug 1704115 - Update xpcshelltest because sniffing happens in more cases now. r=annevk

Depends on D118479

Differential Revision: https://phabricator.services.mozilla.com/D121627

2021-10-25T20:16:00.188000: DEBUG : Did not find a branch, checking all integration branches
2021-10-25T20:16:00.188000: INFO : The bisection is done.
2021-10-25T20:16:00.188000: INFO : Stopped

Looking at the pushlog, commit bb4d0d4d1b1c looks like a good candidate.

Interestingly enough, I had to set "last good version" to 91 in mozregression. Setting it to 92 didn't find a "good" build, but I'm pretty sure this worked fine on v92.

Comment 10

[marko.bozikovic]

Attachment: Sample file

Oh, one more thing. Here's a sample file, as served by TVHeadend. As I've mentioned before, the server sets response header Content-Type to audio/x-mpegurl.

Comment 11

[Marco Bonardo [:mak] (Away 10-21 August)]

yes, the sniffing change looks related, I can't tell if it's doing the right thing or not, I'll let Paul chime in.

Comment 12

[BugBot [:suhaib / :marco]]

Set release status flags based on info from the regressing bug 1704115

Comment 13

[:Gijs (he/him)]

Like bug 1734606, moving back to audio/video as it's an issue relating to the media content type sniffing.

Comment 14

[BugBot [:suhaib / :marco]]

The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.

Comment 15

[Flole]

This is still an issue on Firefox 133 on Windows. The mime-type is shown incorrectly and there is no file extension auto-added on Windows. Firefox on Linux and Mac (and all other tested browsers) properly auto-add the m3u extension.