Closed
Bug 1007998
Opened 12 years ago
Closed 12 years ago
Can't get file from Edgecast CDN
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: richard, Assigned: nmaul)
Details
Attachments
(1 file)
|
1.01 MB,
application/pdf
|
Details |
I'm attempting to test HLS streaming for Air Mozilla.
jwPlayer fails attempting to fetch:
https:// wpc.1237.edgecastcdn.net/crossdomain.xml ...which redirects to:
https://videos.cdn.mozilla.net/crossdomain.xml ...which redirects to:
https://videos.cdn.mozilla.net/crossdomain.xml ...which comes up 404
But https://videos-origin.mozilla.org/manage/crossdomain.xml exists, and I've done a push-to-edge for that file in the Edgecast Media Control Center.
To see the problem live, browse to https://air.mozilla.org/hls-test/
| Assignee | ||
Comment 1•12 years ago
|
||
https://videos-origin.mozilla.org/manage/crossdomain.xml throws a 401 Auth Required for me. IIRC, anything within /manage/ does that. Also IIRC, /manage/ is not allowed on the CDN. :)
https://videos-origin.mozilla.org/crossdomain.xml 404's for me. Perhaps this really is a missing file?
/manage is an alias to /uploads... so...
https://videos.cdn.mozilla.net/uploads/crossdomain.xml
Works!
Would you like this file moved up to the root? Or maybe symlinked, so you can still update it easily if needed?
Flags: needinfo?(richard)
| Reporter | ||
Comment 2•12 years ago
|
||
Yes, a symlmink would probably solve the problem.
Thanks!
Flags: needinfo?(richard)
| Assignee | ||
Comment 3•12 years ago
|
||
All done! Returns a 200 OK for me now. :)
Assignee: server-ops-webops → nmaul
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 4•12 years ago
|
||
Interestingly, https://videos.cdn.mozilla.net/crossdomain.xml returns properly, but that HLS test page still errors out. Perhaps it's hitting the wrong URL right now?
| Reporter | ||
Comment 5•12 years ago
|
||
Turning on the webtools it shows that the request to https://videos-cdn.mozilla.net/crossdomain.xml returns a 301 pointing to https://videos.cdn.mozilla.net/crossdomain.xml, but it doesn't look like Firefox ever requests that file.
I can load it from the address bar with no problem though.
...going back to talk to the webdev guys.
Thanks for the help!
| Assignee | ||
Comment 6•12 years ago
|
||
Ah, yeah... just have them request the videos.cdn.mozilla.net file directly. We've run into a few odd problems like that with videos since we switched the name a month or two ago. :)
| Reporter | ||
Comment 7•12 years ago
|
||
Looks like this is actually an invalid cert problem fetching the original file
https:// wpc.1237.edgecastcdn.net/crossdomain.xml
Alas... I don't have control of which version of the file they request. That's buried deep inside jwPlayer.
(Yet another reason to move to video.js asap).
| Reporter | ||
Comment 8•12 years ago
|
||
OK. Re-opening this one. Edgecast tells me we still "don't have SSL deployed". I thought we had this issue fixed on our Edgecast account:
Click here to view incident: LINK
Short Description: Invalid Cert Attempting to use jwPlayer 6.7 to view HLS stream
Comments:
2014-05-11 17:57:22 - Sanh Luong (Additional comments (client notes))
Hello Richard,
It seems you are trying to request this through https for wpc.1237.edgecastcdn.net, which does not have a SSL cert deployed. I would recommend you push this file through http. Please let us know if there are further questions or concerns. Thank you.
Best Regards,
Sanh Luong
NOC Support
EdgeCast Networks, Inc.
310.479.3200 Ext. 2
1.877.334.3236 Ext. 2
2850 Ocean Park Blvd. Suite 110
Santa Monica, CA 90405
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Comment 9•12 years ago
|
||
Try using cs163.wpc.edgecastcdn.net as the name instead. Edgecast support should have known to tell you about this. :(
| Reporter | ||
Comment 10•12 years ago
|
||
| Reporter | ||
Comment 11•12 years ago
|
||
I don't think there's any way to do that. The JW Player just points at the HLS manifest file at the publishing point (https://wpc.1237.edgecastcdn.net/hls-live/201237/MTV/HLS/Commons.m3u8), and it infers the location of the crossdomain.xml file from that.
The admin interface at my.edgecast.com doesn't give me any way to set up a publishing point on cs163.wpc.edgecastcdn.net.
...and attempting to browse to https://cs163.wpc.edgecastcdn.net/hls-live/201237/MTV/HLS/Commons.m3u8
yields a bad cert error:
cs163.wpc.edgecastcdn.net uses an invalid security certificate.
The certificate is only valid for the following names: *.cdn.mozilla.net, cdn.mozilla.net
(Error code: ssl_error_bad_cert_domain)
...am I missing something obvious here?
Attaching the PDF of the Edgecast HLS how-to docs in case they help.
| Assignee | ||
Comment 12•12 years ago
|
||
Best bet then would be to push this off to our rep... Dan Solnicki <dan@edgecast.com>. I not that "HTTPS" appears nowhere in that document. Perhaps they're just not able to handle secure live streaming.
In any case, he's the best person to ask at this point, I think.
| Assignee | ||
Comment 13•12 years ago
|
||
From email it sounds like Edgecast's HLS system simply doesn't support HTTPS right now. :(
Closing this out ... don't think there's anything we can do here.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → INCOMPLETE
Updated•7 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•