I apologize for my English.

firefox 7.0.1 does not open local addresses.

example:

- Access to the router

192.168.10.1

- Message:

Error corrupted content

 The page you are trying to view can not be displayed because an error was detected in the transmission of data.
 The page you are trying to view can not be displayed because an error was detected in the transmission of dados.Por please contact the owner of the website for information about the problem.

If using Internet Explorer, the address works.

peço desculpas pelo meu inglês.

o Firefox 7.0.1 não abre endereços locais.

exemplo:

- aceder ao router

192.168.10.1

- mensagem:

Erro de conteúdo corrompido

A página que está a tentar visualizar não pode ser apresentada porque foi detectado um erro na transmissão de dados.
A página que está a tentar visualizar não pode ser apresentada porque foi detectado um erro na transmissão de dados.Por favor, contacte o dono do sítio web para o informar sobre este problema.

Se utilizarmos Internet explore, o endereço funciona.

The problem is that certain servers are configured wrong. In Firefox 7, if the server is sending two different things about the URL of page you're on (often, it's just missing an index.html or a leading www) and since that can sometimes indicate that the contents of the page have been tampered with, you're given this warning.

This is happening here probably because your affiliate is adding extra headers that don't line up exactly. You should contact the people running the affiliate servers and point them to https://bugzilla.mozilla.org/show_bug.cgi?id=681140

Thanks for the replies. You are right, it's to do with the headers. The response from my affiliate is "we'll change your password" ! I've got round it so far by continually clicking "Try Again" which usually works after 3-4 attempts but it's a pain. I've also now discovered it happens using Chrome (I won't use IE). I will send them to your link Cww and try to get them to change their headers. Thanks

Hi. Same here, as "hdsoares" with D-Link router D-Link DVA-G3170i. And ask to dlink support to slove this issue, better to buy a new router. I don't think they will slove that in a short term.

I don't like to use IE, but tstill works with this router model.

Here's my perl download script which has been working for years but now fails with "corrupted content" when download is attempted with Firefox v. 7:

print <<THE_END;
Content-type: application/x-msdownload; name=$display_name;
Content-length: $filesize;
Content-Disposition: attachment; filename=$display_name;
Content-Description: $display_name

THE_END

  open(FILE, "$filename") || print "Error opening database file";
  while(<FILE>) { print }
  close(FILE);

 $download_attempts--;
 &rewrite_database;

 exit;

I'm afraid I'm not a perl or HTML expert. Can someone please explain what's wrong with the header that's causing the download errors?

I had the same error while downloading a file from one of website. The error was due to Content-Length.

Ex. header('Content-Length: ' . filesize($filename));

Commenting the above line resolved the problem, allowing the file to download as before.

Ex. //header('Content-Length: ' . filesize($filename));

Hope this helps someone.

Cheers, Sarjya

I get this on firefox. I get this on waterfox. I get this on nightly. I don't get it on chrome. I don't get it on internet explorer. I don't get it on comodo dragon. I don't get it on arora. I don't get it on konqueror...... Anyone noticing a pattern here?

I'm willing to admit that it's probably something to do with my isp server, so Mozilla can feel holier than thou about it, but if that's the way they insist on going, I suggest that the next time they upgrade, they call their browser Canute.

I just want to thank Sarjya for posting that solution. We have a video download site and some files are over 2GB which was causing download problems in some browsers (including the "Corrupted content" error in Firefox). I commented out the content-length line in the PHP file that handles the downloads and the problem went away :)

Cheers, Chris