01-19-2012 08:35 AM
We are using the same Rendition URL to set up a
Download link, and it looks like this
When we click on it , it opens the video in a new window and plays it. I do
not want this Rather I want link to popup window asking to save the file to the local machine. How can
this be achieved?
01-19-2012 10:19 AM
01-19-2012 01:37 PM
HG is spot on with that comment.
Only firefox renders the sweet download links. Remember, invoking the API is basically returning XML - and each browser has their own way of rendering the content. You need to do some programming to make the magic happen.
01-25-2012 12:11 AM
This is interesting, if i were hosting this video on my server, I would add the content-disposition flag to the response headers to force the different browsers to download the video, instead of trying to play it. I'm having the same issue, can someone point me to an example of this custom code proxy you are referring to above?
04-05-2012 08:45 AM
I would like to ask this question again.
The only way I know to force browsers to save .mp4 videos to disk is to send content-disposition:attachment header from the server. http://brightcove.vo.llnwd.net/ server does not serve this header with .mp4 files, so our users see a video playing in a new window, instead of being downloaded.
Is there any way to ask http://brightcove.vo.llnwd.net/ server to add content-disposition:attachment header? Perhaps with a query string parameter?
04-05-2012 10:13 AM
great idea on adding the content-disposition:attachment header with a query string. Lets see what brightcove has to say about that.
Not sure how using a proxy would involve a huge bandwidth impact on the server since you would only be pinging the server for a few bites to help you download the MP4 which then will be downloaded from BrightCove. Here is a quick dirty PHP sample to get you started using the file pointed out at the begining of the thread:
header('Content-Disposition: attachment; filename="romedemo.mp4"');
I hope this helps.
04-10-2012 05:34 AM
Correct me if I'm wrong, but file_get_contents($url) will attempt to load the whole file located at $url into web-server memory. Because the full-size videos are anywhere from 100Mb up, this will either time-out, or consume all available memory on the web server and crash.
I'm not aware of any mechanism in HTTP by which web server can reply to the browser "please take these content-disposition headers, but then issue another HTTP request to the Brightcove server and load actual video directly from there".