M
Matt Johnson
Hi,
I am suffering with problems whereby visitors to my website
are hitting the bug mentioned in KB308090. The website is
PHP-based and uses the HTTP Location: header to provide an
*FTP* link to the ZIP file to the user. However IE fails to
save the file in Temporary Internet Files, and so users
clicking 'Open' are presented with what appears to be a
"blank" ZIP file.
Does anyone know what variables tickle this problem? It
apparently did not happen on my old server which rendered
an HTML page with HTTP-EQUIV Refresh -- but I tried this on
my new server and I still get the same problem.
Methods I have tried all suffering with the same problem:
* Location: ftp://... header
* Refresh: 0; url=ftp://... header
* meta http-equiv="refresh" content="0; url=ftp://..." in a
valid web page (this one apparently used to work).
I've seen this problem reported previously where the
download has taken place over an HTTP connection, but have
not seen much mention of it with FTP.
Does anyone have any insight into this problem, or even
when MS will release a patch to fix the outstanding KB issue?
Thanks,
--Matt
I am suffering with problems whereby visitors to my website
are hitting the bug mentioned in KB308090. The website is
PHP-based and uses the HTTP Location: header to provide an
*FTP* link to the ZIP file to the user. However IE fails to
save the file in Temporary Internet Files, and so users
clicking 'Open' are presented with what appears to be a
"blank" ZIP file.
Does anyone know what variables tickle this problem? It
apparently did not happen on my old server which rendered
an HTML page with HTTP-EQUIV Refresh -- but I tried this on
my new server and I still get the same problem.
Methods I have tried all suffering with the same problem:
* Location: ftp://... header
* Refresh: 0; url=ftp://... header
* meta http-equiv="refresh" content="0; url=ftp://..." in a
valid web page (this one apparently used to work).
I've seen this problem reported previously where the
download has taken place over an HTTP connection, but have
not seen much mention of it with FTP.
Does anyone have any insight into this problem, or even
when MS will release a patch to fix the outstanding KB issue?
Thanks,
--Matt