IE cannot load bmp file called unicode

I have a web application that allows users to upload and download image files by clicking buttons on a web page. The user of this page reports that IE 7 and 8 cannot download files when files have Unicode paths. IE asks the user for a dialog with the message: "Internet explorer cannot upload (file) to (web server)."

The problem only occurs in IE. Unfortunately, I could not reproduce the problem using these versions on my machine.

My question is what can cause this, and how can I prevent it? I read about cache management issues (I currently have no-cache installed); however, I do not use HTTP-S, and the problem only occurs with file names containing Unicode characters.

Update: The problem occurs when the user tries to download the path to the bmp file. Custom file paths loaded successfully. Could it be that Paint is causing problems?

Javascript sets add an iframe that points to the URL associated with the file.

+4
source share
3 answers

Thus, an error only occurs if you insert the content header into the application. As soon as I removed the header from my HTTP response headers, the problem was resolved.

If you set the mime type to an unknown value, the bitmap will not be displayed as an image and will be treated as an attachment.

0
source

Thanks for your updated comments.

It could be:

  • Web server
  • Your customer’s browser extensions
  • Your file name is too long (as shown below, but v old articles)

I think this is most likely number 2, since you cannot reproduce the problem (you are using real versions of browsers, right?).

You can ask them to run Internet Explorer without extensions by running iexplore -extoff , and look, it doesn't matter. They can also check their security settings.

I found with IE that this could be a lot of things causing the problem, as I mentioned before, before I had the problem of “inability to download”, because for some reason our server had double gzipping content, only with IE, and IE obviously didn’t really like it.

I know that these articles are very outdated, and I am sure that they are not applicable, however they may be relevant: http://support.microsoft.com/kb/816868 http://support.microsoft.com/kb/812935 / en-us

+1
source

I think you need to encode the file name in the download link. The problem may be that the browser does not know the encoding of the web server file system, so different browsers may accept different assumptions about the encoding of the file system. Url coding should solve this ambiguity.

0
source

All Articles