Supposed to be like that, because they are media items if you look at the URL it is a reference and no file extension so the browser does not handle it. This then allows a straight download and thus can record the stats for the download.
This is itended and wanted feature because in cases of media downloads you want them to do just that, download the item not view it in the browser
Thanks Liam...I thought it might have something to do with the extension. And great point about the downloading vs. viewing...I'll try that reasoning with my client
If it comes to the streaming options you see that will keep the file extension so you can create something like a playable podcast.
A download is not always desired.
For instance, I'm working on a secure zone portal. Documents are stored securely only through MediaDownload. We want the links to the documents to open for viewing, not for download.
Would be open to another method, if you have one.
File extensions are a red herring — the behaviour is set by the
In particular, BC sends the header
Content-Disposition:attachment; filename=foo%20bar.pdffor media downloads, preventing the browser from opening it inline. That header is omitted for files added through the file system (SFTP / file manager), so the browser uses its default behavior.
What the browser does with the file doesn't change the way the file is downloaded; stats would be recorded either way.
I'd be happy to use regular file uploads to a folder, if that folder could be made secure within a zone.
The only way I know of (in BC) to make a file secure is to do it with Media Download... unless there's another way?
In this case, MediaDownload is a good feature. I just want to choose the behavior, like we can with target _blank settings for hyperlinks.