Closed Bug 882114 Opened 12 years ago Closed 12 years ago

App videos do not work in app details page

Categories

(Marketplace Graveyard :: Consumer Pages, defect, P2)

Product:
Marketplace Graveyard
Component:
Consumer Pages
Platform:
x86_64
Windows 7
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED
Milestone:
2013-08-01

People

(Reporter: julian.mozbugs, Assigned: basta)

References

(
URL
)

Details

Steps to reproduce: 1. Load an app that has a video preview (ex. https://marketplace-dev.allizom.org/app/test-app-paidbimmer/ ) 2. Click on the video thumbnail. Expected results: The video starts playing in the displayed window. Actual results: An attention icon is displayed. The video is not working. Notes/Issues: Verified on FF24 (Win 7). Screencast for this issue http://screencast.com/t/WfRAdpnvptmY
The CDN is responding with a one-byte 206 Partial Content response. This sounds like an ops issue, yes?
Assignee: nobody → jthomas
Priority: -- → P2
Component: Consumer Pages → Server Operations: AMO Operations
Product: Marketplace → mozilla.org
QA Contact: oremj
Target Milestone: 2013-06-13 → ---
Version: 1.0 → other
What is the path to the video on this page?
Flags: needinfo?(mattbasta)
https://marketplace-dev-cdn.allizom.org/img/uploads/previews/full/98/98993.webm?modified=1371040578 I'm not sure what kind of demon magic is going on, but when I hit the video directly, it makes three requests to the server.
Flags: needinfo?(mattbasta)
The nginx configuration for this domain looks okay and webm video plays correctly in browser when visiting the url directly. Are we setting the Range headers here correctly when requesting the video?
I don't think this is a server bug. The web console shows the video being loaded correctly. Does this work locally?
Component: Server Operations: AMO Operations → Consumer Pages
Product: mozilla.org → Marketplace
QA Contact: oremj
Version: other → 1.5
Assignee: jthomas → mattbasta
Target Milestone: --- → 2013-08-01
https://github.com/mozilla/fireplace/commit/a85daaafbd5a2679eb1c1992b28659057c72dad2 Turns out the API changed at some point and we were looking at the "type" field instead of "filetype".
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: 2013-08-01 → ---
Target Milestone: --- → 2013-08-01
Verified as fixed in https://marketplace-dev.allizom.org/ on FF25 (Win 7). Postfix screencast http://screencast.com/t/YQkH7X42kK Closing bug.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.