MP3 links in the Studies view work on some kind of redirection--the link to the mp3 is a PHP request, which then redirects to the proper URL. (The podcast page doesn't use these redirections.)

For some reason, these links don't work on my iPhone. I get an error message, "Download Failed. Safari cannot download this file."

Any idea what's going on?

Would it be possible to change the download links so that they don't use redirection? In other words, write the direct URL into the HTML of the Studies views, like you do with the podcast RSS file?

Linking directly to the mp3 files, would cause the default "player" to open them directly rather than to display the download dialog box.

to fix this, the links point to a php file which sends headers to retrieve the particular mp3 file.

Try turning on/off compatibility mode (although I don't think it would fix your problem, because it essentailly does the same thing, just from a different server)

Do you mean that the browser would open it in something like quicktime, instead of opening the "save file" dialogue?

If so, hmm... That's actually a per-browser setting for the default behavior of clicking on an mp3 link--you can have your browser configured to save an mp3 when you click on it, instead of opening it. But most people don't have it that way, or don't know how. So I understand the need for a fix.

Is there no other way? Something like a parameter in the href tag?

I'm wondering if removing the redirection would allow links-with-spaces, too, instead of %20's.

Perhaps we can add an option to determine how download links are generated:

• href
• send Headers
• send Headers (compatibility mode)

Tom?

Sounds possible - however, Eugen is the brains behind the download function beyond my very basic one. Hopefully he can chime in.

Tom

As I mentioned in another thread, I'm also wondering about the Content-Disposition header, where the filename is set. If that's only used by the web browser for creating the filename, and if spaces are allowed in that context (even though they're not allowed in URLs), then you could change the encoding--encode with spaces instead of %20's.