I'm not seeing that issue.

You can get a "Corrupted Content Error" or errors in the data transmission if there are multiple location redirects send via the HTTP response headers.

• bug 681140 - Corrupted Content error due to multiple Content-Disposition header field instances

Older post by you about this issue (no replies).

• [/questions/888583]

I don't get a "corrupt Content Error" but an alert: "The page you are trying to view cannot be shown because an error in the data transmission was detected.".When I then use RightClick Open In IE Tab, I can acces the site again or I have to clear mij history. Also the alert never occurs is Internet Explorer so I gues it's a FF isue. The website that is causing the problem is my own website and runs in my Network on a different PC. The problem did NOT occur in the previous versions of FF

As an extra I send you hereby a screenshot

From the http log:

nsHttpTransaction::ParseHead [count=236]
nsHttpTransaction::ParseLine [HTTP/1.1 304 Not Modified]
nsHttpResponseHead::ParseVersion [version=HTTP/1.1 304 Not Modified]
Have status line [version=11 status=304 statusText=Not Modified]
nsHttpTransaction::ParseLine [Content-Type: text/html]
ParseContentType [type=text/html]
nsHttpTransaction::ParseLine [Content-Length: ]
invalid content-length!
nsHttpTransaction::Close [this=4e23aa0 reason=804b001d]
nsHttpConnectionMgr::ReclaimConnection [conn=d1e980]
STS dispatch [3b04b20]
nsHttpConnection::CloseTransaction[this=d1e980 trans=4e23aa0 reason=804b001d]
nsHttpTransaction::Close [this=4e23aa0 reason=804b001d]

Firefox is receiving malicious content-length
Reason 804b001d ->> NS_ERROR_CORRUPTED_CONTENT
A transport level corruption was found in the source document. for example
a document with a calculated checksum that does not match the Content-MD5
http header.

And what does this all mean in plain human language? Sorry but I don't speak computer language very well ;-)

It is my experiance that the problem only occurs in the latest version of FF. I installed an older version of FF i.e. version 3.6.23 and than version doesn't give any problems.

Er wordt een webpagina ontvangen met ongeldige / kwaadaardige informatie over de grootte van de verzonden gegevens. Dit gebeurt normaal gesproken vooral wanneer een webserver is geïnfecteerd met een computervirus. Sinds Firefox 7 wordt dit niet meer getolereerd, daarvoor nog wel. Het probleem is, dat wanneer je deze fout zou negeren, je nooit zeker weet of een webpagina compleet is of dat er iets aan is veranderd door een virus. Voor de veiligheid op internet is het dus beter om dit helemaal niet toe te staan en streng op te treden. Tenminste, dat vindt Mozilla en ik persoonlijk ook.

Aangezien het hier om mijn eigen website gaat en ik zeker weet dat deze niet is besmet met een virus of malware vind ik dit zeer vreemd. Na een reset van de history gaat het ook steeds een poos goed. Wanneer ik na een alert de link open in IE Tab gaat het ook goed. In InternetExplorer 9 ondervind ik ook geen problemen. Het lijkt erop dat door het snel opeenvolgen van nieuwe updates van FF de zorgvuldigheid hier en daar een steekje laat vallen, wat je ook zou kunnen concluderen over de vele klachten die in dit forum te lezen zijn.

That page opened normally for me. I am using Firefox on a Mac.

@finitarry
Interesting. Did you read from the cache while making the logfile? I am only getting an errorpage when hitting F5. When I open it for the first time or hit the ctrl+F5 it will load just fine (Win Vista). I think the problem starts when doing a validation request after checking the cache. My big question is: Why am I getting this "invalid content-length!"?

Looks that the server isn't sending a Content-Length in the response headers and that Firefox falls over that when fetching from the cache.
It only works with the disk cache disabled and in Private Browsing mode with the memory cache disabled or by clearing the cache.
It also works in off-line mode.
So it looks that the solution would be to configure the server to send the content-length.

HTTP/1.1 200 OK
Content-Type: text/html
Last-Modified: Fri, 28 Oct 2011 13:40:21 GMT
Vary: Accept-Encoding, User-Agent
Content-Encoding: gzip
Connection: Keep-Alive
Keep-Alive: timeout=150000, max=10
Transfer-Encoding: Chunked
Date: Fri, 28 Oct 2011 23:03:09 GMT
Server: Abyss/2.6.0.0-X1-Win32 AbyssLib/2.6.0.0

Thanks, for helping me finding a cure for my problem. Can you tell me where to implement the code. I'm not that good in programming, you know

It would be best to contact the company that hosts your website and ask them to look into it.
You may not have access to those files.

I host my own server on an old laptop. The server software is Abyss (www.aprelium.com) The website is just for our hobbies, Motorbike riding and mountainbiking. I run my website for more than 10 years now and never had any problems. I am annoyed by the fact that the problem occurs after the upgrade to version 7 of FF. In the old(er) versions AND in IE there are no problems what so ever, so why shoult I change something in MY server because FF(7) is causing the problems!

Maybe someone on MozillaZine knows this server software and can come up with a solution.

You can try ask advice at the mozillaZine Web Development/Standards Evangelism forum.
The helpers at that forum are more knowledgeable about web development issues.
You need to register at the mozillaZine forum site in order to post at that forum.
See http://forums.mozillazine.org/viewforum.php?f=25