1. 21 Mar, 2014 2 commits
    • Fix a url processing error in 02_html5_video.js · ce1b6231
      As the code in this .js will break the url's integrity when there is already a query string inside the video source's url and cause the url to be invalid in some cases (for example, when working with a url from Windows Azure's Media Service, the appended '?' will cause the url being invalid).
      I modified the code by first checking whether the url has already had a query string, and if so, then use '&' instead of '?' to prevent the breaking, and it works for the url from Windows Azure's Media Service.
      louyihua committed
    • Fix the url processing error when there is a query string inside the video source's url · d76c3dfc
      1. In video_module.py, rewrite the get_ext() function to use the built-in urlparse module to parse the input filename first and then get the file's extension name from the parsed path.
      2. In test_video.py, add two test cases (one with query string while the other without) in order to test the rewritten get_ext() function.
      louyihua committed
  2. 19 Mar, 2014 1 commit
    • Fix incorrect parse of url in video_module.py · a458b90d
      Sometimes the video url may look like 'http://abc.com/path/video.mp4?xxxx'.
      (For example, the Windows Azure's media service will offer such type of url.)
      The original code in video_module.py will produce 'mp4?xxxx' instead of 'mp4'
      as the extension of a filename for such type of url, and therefore the video
      will be non-playable. The fix here uses the built-in urlparse module to retrive
      only the path component from a url and therefore the extension 'mp4' will be
      correctly fetched.
      louyihua committed
  3. 17 Mar, 2014 15 commits
  4. 15 Mar, 2014 2 commits
  5. 14 Mar, 2014 7 commits
  6. 13 Mar, 2014 13 commits