In article <>,
says...
> I've tried with a lot of HTTP headers now and not any solution 
>
Continuing, I've found something ; even if it's not about Perl, it may
interest some.
Searching, I've finally found an HTTP header which works under a local
Apache/Windows :
print "Content-Type: application/octet-stream\n";
print "Content-Length: $size\n";
print "Content-Disposition: attachment; filename=$file\n";
print "Pragma: public\n";
print "Cache-Control: must-revalidate, post-check=0, pre-check=0\n";
print "Expires: 0\n\n";
The problem is that it still didn't work under remote Apache/FreeBSD. IE
fails to find info about file, then display an error.
Searching again and again, I've found an MS article at
http://support.microsoft.com/default...b;en-us;812935 talking
about ""Internet Explorer Cannot Download" Error Message When You Use an
HTTPS URL to Open an Office Document or PDF File".
Well, in my case, it's not an HTTPS url and not about PDF/DOC/XLS/MDB
document... But, I've tried what they say :
********
Article ID : 812935
Last Review : November 15, 2007
Revision : 2.5
CAUSE
This issue may occur if any one or more of the following conditions are
true: ? The Do not save encrypted pages to disk check box is selected in
Internet Explorer 6.0 SP1.
? The server sends the "Cache-Control: No Store" header.
? The server sends the "Cache-Control: No Cache" header.
RESOLUTION
A supported hotfix is now available from Microsoft. [they don't give any
url for doanload]
WORKAROUND
To work around this problem, make sure that Do Not Save Encrypted Files
check box is not checked and that the server does not send the "Cache-
Control: No Store" or the "Cache-Control: No Cache" header.
You may also be able to work around this problem by using an HREF to
load the document.
Note This method does not work if the server uses the "Cache-Control: No
Cache" header.
**********
Thus, I've unchecked the "Do Not Save Encrypted Files" IE's check box in
its options... And magically, it works !
Good for me, but wrong for my visitors if they have this case checked.
How to manage this IE6 Bug according to you ???