Metadata
- Source
- VP-90
- Type
- Bug
- Priority
- Major
- Status
- Closed
- Resolution
- Fixed
- Assignee
- Cindy Li
- Reporter
- Michelle D'Souza
- Created
2012-01-17T15:20:31.405-0500 - Updated
2013-01-28T09:25:22.684-0500 - Versions
- N/A
- Fixed Versions
- N/A
- Component
- N/A
Description
It appears that when the demo is loaded from localhost it does not load the videos that are specified with a relative path.
Comments
-
Anastasia Cheetham commented
2012-01-23T14:28:55.405-0500 I've tested this in a few browsers, with the following results:
FF (latest) on Mac: fails (response code for the video request is "206 Partial Content")
Chrome (latest) on Mac: works
Safari (latest) on mac: works
Opera (latest) on mac: worksWindows in general: My VM can't seem to connect to my localhost, so I can't tell.
-
Anastasia Cheetham commented
2012-01-23T14:49:16.944-0500 Investigating the 206 status code... This is described as:
"The server is delivering only part of the resource due to a range header sent by the client. The range header is used by tools like wget to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams."I checked the header. The request header does include a range, which is a requirement for the partial response.
-
Anastasia Cheetham commented
2012-01-23T15:38:13.167-0500 I notice that Chrome is also getting a 206 for the video, however Chrome will play the video regardless. FF will not.
-
Cindy Li commented
2012-01-24T13:19:41.065-0500 This issue is due to the misconfiguration of Apache web server that results in the wrong MIME types being sent.
Adding the lines below into Apache configuration file (httpd.conf) resolves the problem:
AddType video/ogg .ogv
AddType video/mp4 .mp4
AddType video/webm .webm -
Cindy Li commented
2012-01-24T13:20:39.512-0500 Issue solved by adjusting the Apache configuration. No changes are made into video player scripts.