.NET CLR 1.0.3705 difference cause MSIE downloaded problems?

  • Thread starter Thread starter Psychomation
  • Start date Start date
P

Psychomation

Hello,

I am trying to resolve an issue where sending a file from a server to a
browser using PHP will give an error message in MSIE, but the file does
download from the server. The exact error is "There was an error opening
this download. This file cannot be found". So far, all I've seen is that
MSIE 6 using .NET CLR 1.0.3705 yields this message whereas our tests with
..NET CLR 1.1.4322 work as expected.

Is there a workaround for this other than forcing the user to update (and
will the update solve it, i.e., is this a known issue)? Are extra headers
needed with 1.0.3705 to send files for downloading with the proper
disposition?

Any other links to solutions or suggsts welcome!

tia
 
I am trying to resolve an issue where sending a file from a server to a
browser using PHP will give an error message in MSIE, but the file does
download from the server. The exact error is "There was an error opening
this download. This file cannot be found". So far, all I've seen is that
MSIE 6 using .NET CLR 1.0.3705 yields this message whereas our tests with
.NET CLR 1.1.4322 work as expected.
Click to expand...

While it would have been interesting to know why the difference between
versions, it was more important to get it fixed. Of the many, many pages
about this issue (PDF/MSIE) on the web, one of them mentions adding
Access-Size: Bytes header. Something between PDF and .NET CLR 1.0 makes
them not like each other apparently.

Issue closed (afaic)
 
Back
Top