1365512 - Media could not be played on Twitter -- media returns 404

Status: RESOLVED DUPLICATE of bug 1374510

(Core :: DOM: Core & HTML, defect)

Description

[:gerard-majax]

STR:
 1. Load a tweet with media https://twitter.com/PocahontasPrncs/status/864475833876000773
 
Expected:
 Media can be played

Actual:
 Error with "This media could not be played"

Web console shows that CSP blocked loading of MP4 file (french):
> Content Security Policy: Les paramètres de la page ont empêché le chargement d’une ressource à self (« script-src https://twitter.com http://localhost:* http://localhost.twitter.com:* https://*.twitter.com https://*.twimg.com https://vine.co https://*.vine.co https://*.periscope.tv https://*.pscp.tv »). Source: onfocusin attribute on DIV element. 864475833876000773
> Le chargement HTTP a échoué avec l’erreur 404. Le chargement de la ressource média https://video.twimg.com/tweet_video/C_88LqJU0AASyom.mp4 a échoué.

100% on https://hg.mozilla.org/mozilla-central/rev/e66dedabe582ba7b394aee4f89ed70fe389b3c46

Comment 1

[:gerard-majax]

FYI, I'm not able to reproduce that with a clean profile.

Comment 2

[:gerard-majax]

And just restarting Firefox it is working again ...

Comment 3

[Daniel Veditz [:dveditz]]

I'm not seeing a problem. Reopen if it recurs in a reproducible way. Maybe one of your add-ons?

Comment 4

[:gerard-majax]

It does re-occurs:
 > https://twitter.com/SNCF/status/873193886872723458

Console shows 404 errors on media:
> Le chargement HTTP a échoué avec l’erreur 404. Le chargement de la ressource média https://video.twimg.com/tweet_video/DB40qxaW0AE4S7U.mp4 a échoué.

Loading the same media URL by hand in another tab works.

Comment 5

[:gerard-majax]

Attachment: Console error

Comment 6

[:gerard-majax]

Attachment: Working media

Comment 7

[:gerard-majax]

Attachment: MP4 returns 404

Comment 8

[:gerard-majax]

New element:
 - loading the URL works in a non-container tab
 - reproduced 404 in a container "personnel" tab

Force-reloading the URL in container tab "personnel" ends up working.

Comment 9

[:gerard-majax]

It is happening again today. Nightly is https://hg.mozilla.org/mozilla-central/rev/fe809f57bf2287bb937c3422ed03a63740b3448b

Reproduced at least on https://twitter.com/bouyguestelecom/status/875739073826213888 with media https://video.twimg.com/tweet_video/DCc__KEWAAAymuq.mp4 ; curl at the same moment returns 200 OK.

Comment 10

[:gerard-majax]

Attachment: Capture d'écran de 2017-06-16 17-38-11.png

Looks like I am reproducing that from time to time :(. What seems to be consistent, though, is that when it happens in the container my twitter tab is, it works in a non-container tab right at the same moment.

Comment 11

[Daniel Veditz [:dveditz]]

baku: any ideas about what could be going on here? Given comment 8 (force-reload makes it work) could be a caching issue?

Comment 12

[Andrew Overholt [:overholt]]

There's a private email thread ongoing about this with some Twitter people where they are investigating. I'll point them to this bug.

Comment 13

[Andrew Overholt [:overholt]]

Oh, and it appears it's an internal Twitter issue that they've identified and are working on a fix for.

Ben Kelly filed bug 1374510 about better handling of 404s.

Comment 14

[:gerard-majax]

(In reply to Andrew Overholt [:overholt] from comment #13)
> Oh, and it appears it's an internal Twitter issue that they've identified
> and are working on a fix for.
> 
> Ben Kelly filed bug 1374510 about better handling of 404s.

Awesome. I also spotted the issue this morning on my desktop running latest stable on Debian (53 I guess), but with containers as well. Does that match the observations or are we starring a slightly different issue ?

Comment 15

[Andrea Marchesini [:baku]]

Removing NI. It seems that it's not a container bug. NI again if I'm wrong.

Comment 16

[Andrew Overholt [:overholt]]

(In reply to Alexandre LISSY :gerard-majax from comment #14)
> (In reply to Andrew Overholt [:overholt] from comment #13)
> > Oh, and it appears it's an internal Twitter issue that they've identified
> > and are working on a fix for.
> > 
> > Ben Kelly filed bug 1374510 about better handling of 404s.
> 
> Awesome. I also spotted the issue this morning on my desktop running latest
> stable on Debian (53 I guess), but with containers as well. Does that match
> the observations or are we starring a slightly different issue ?

I'm not sure. Let's leave this open and when I hear back from the Twitter folks I'll comment here and we can see if it's still reproducible. Thanks.

Comment 17

[Andrew Overholt [:overholt]]

Oh, and I can reproduce and I'm not using containers.

Comment 18

[Daniel Veditz [:dveditz]]

Moving to Generic DOM. It doesn't seem to be related to containers and our CSP processing should be the same as chrome wrt what Twitter uses.

Comment 19

[Ben Kelly [:bkelly, not reviewing]]

We have some logs/analysis going on over in bug 1374510.