> Our Rails application allows WAV file downloads. The user clicks on a > link, or > clicks a button, and the WAV file gets sent as a response, using > send_file. > > It looks like IE is discarding the initial WAV file and passing the > URL to Windows > Media Player. Windows Media Player then re-requests the file!! > > In addition to the performance problems, this design problem causes > failures in the > case of the download being initiated from a POST, since the re-request > from the > Media Player is only a GET, not a POST. > > How do I prevent this re-request?
I don't think you can. Years ago a collegue had an issue with large PDF's being sent as a result of a POST. The PDFs that were under 1meg IE would download and then give that file to Adobe. Above 1meg and it would download some if it, then pass it to Adobe -- losing all the POST variables in the process. The only solution we found was to convert that POST into a GET (or redirect it to a temp url that is a get). And suffer with the re- sending. This was probably 6 years ago though... but sounds like it hasn't changed one bit. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
