Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: Firefox Corrupted Content Error

  1. #11
    Join Date
    Aug 2010
    Chicago suburbs
    Blog Entries

    Default Re: Firefox Corrupted Content Error

    I'll add my two cents here.

    I often see a corrupted content page.

    Usually, it occurs when the login cookie has expired, but there is some other opensuse cookie which has not yet expired.

    When it happens -- if it is late enough in the day, then I decide that's enough of the forum for today. But if it happens earlier in the day, I go to the forum main page. Sometimes, I can login again there, which solves the problem. And sometimes I just see a clean forum page -- which also solves the problem, except that any attempt to post will get me a login page.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  2. #12

    Lightbulb Re: Firefox Corrupted Content Error

    Quote Originally Posted by DaAwesomeP View Post
    When I clicked on a link in a notification email, Firefox refused to load the page and gave me this error:

    Corrupted Content Error
    The site at has experienced a network protocol violation that cannot be repaired.
    The page you are trying to view cannot be shown because an error in the data transmission was detected.
        Please contact the website owners to inform them of this problem.
    This is a Windows 10 machine with the latest Firefox. Not sure what that means exactly, but there must be something wrong with Apache or PHP somewhere.

    Try this simple solution. Worked for me:
    Ctrl + F5

  3. #13
    Join Date
    Dec 2008
    FL, USA

    Default Re: Firefox Corrupted Content Error

    I filed a month after this thread. The problem continues to be sporadic. It happened again 2-3 days ago. It could be because performance in general is so much worse than average here because of the continuous redirections between Western USA and Europe while my typical 10+ tabs at once to the various subdomains, all of which load different content according to login status, are open. Load times are typically average, but latency is typically 3X-4X worse than average. No other routinely used sites put "waiting on ..." on the statusbar as much, both frequency and duration. Complete timeouts resulting in white page results searching B.O.O. are common. Errors during zypper refresh are also common, not much while updating. I really don't have much trouble using the web, except on, which after duckduckgo, google and wikipedia are probably my first or second most used "site".
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts