|Starting download from IE in Windows|
doesn't work under SSL.
| 6:48 pm on Oct 23, 2002 (gmt 0)|
The following code works perfect on any browser, including IE in Windows if the script is under regular HTTP (http:/blahblah/download.php):
However, if I put it under SSL (https://blahblah/download.php) IE in Windows will NOT download the file, saying after a while that the operation timed out.
Do you know any work-around for this situation?
| 8:54 am on Oct 25, 2002 (gmt 0)|
is it possibly an inherent attribute of https?
Anyone have any ideas?
| 8:55 am on Oct 27, 2002 (gmt 0)|
Maybe I'm saying an enormous idiocy [I know C/Perl, not PHP], but are you sure that PHP without additional modules can handle encrypted HTTP requests?
| 5:33 pm on Oct 28, 2002 (gmt 0)|
absolutely, in fact (I didn't mentioned it before), every other browser I've tried, can handle the script under SSL, except IE for Windows.
The other funny part is that my Apache log shows that the file was in fact delivered, but it seems that the browser never knew about it.
| 6:13 pm on Oct 28, 2002 (gmt 0)|
Yes, in fact I've said an idiocy :)
I know that IE don't trust the mime-type 'sent' by the server [the Content-type header], instead he brainless try to read the first bytes of a 'non plain text/html' file, with the goal of understanding what it is.
So, maybe IE try to read the first encrypted bytes, and hangs on them.. ;)
1] some obscure Micro$oft proprietary Content-type..
2] A RewriteRule or BrowserMatch that redirect any '*.mp3' browser's request to normal, non-encrypted port 80 [easy, if you want I post the snippet].
But I don't know if this is acceptable for you.. :)
| 6:28 pm on Oct 28, 2002 (gmt 0)|
Aha! that must be it!
I don't like this solution, but my download script is now a regular port 80 HTTP request. :(
I'll keep on searching...
Thank you cminblues!