X
Нажмите здесь, чтобы перейти на мобильную версию сайта.

Форум поддержки

Content corrupted error on my website, and I can't figure why

Размещено

We've launched our new website this week, and we're getting some 'content corrupted error' in Firefox. It's not at every time, but close to 40%. The other browsers are fine.

I saw posts about duplicate headers, but I haven't seen any.

I tried enabling HTTP log (https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging), but I couldn't see anything that could help me figure out which part of Firefox doesn't like.

The website is https://www.longueuil.quebec

Any idea?

We've launched our new website this week, and we're getting some 'content corrupted error' in Firefox. It's not at every time, but close to 40%. The other browsers are fine. I saw posts about duplicate headers, but I haven't seen any. I tried enabling HTTP log (https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging), but I couldn't see anything that could help me figure out which part of Firefox doesn't like. The website is https://www.longueuil.quebec Any idea?

Дополнительные сведения о системе

Установленные плагины

  • ActiveTouch General Plugin Container Version 105
  • Adobe PDF Plug-In For Firefox and Netscape 11.0.01
  • Citrix Online App Detector Plugin
  • Google Update
  • NPRuntime Script Plug-in Library for Java(TM) Deploy
  • Next Generation Java Plug-in 10.25.2 for Mozilla browsers
  • NPWLPG
  • WebViewer Plugin
  • Shockwave Flash 18.0 r0
  • 5.1.40728.0

Приложение

  • User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0

Дополнительная информация

FredMcD
  • Top 10 Contributor
4266 решений 59829 ответов
Размещено

Firefox; https://www.longueuil.quebec/fr Corrupted Content Error


Win IE works fine

I've called the big guys to help you. Good luck.

Firefox; https://www.longueuil.quebec/fr Corrupted Content Error Win IE works fine I've called the big guys to help you. Good luck.
cor-el
  • Top 10 Contributor
  • Moderator
17567 решений 158879 ответов
Размещено

I think that the problem is the that page source start with a rather long JavaScript. Firefox is searching for the HTML tag with the content encoding and doesn't find it in the first 1024 bytes as you can see in the Web Console (Firefox/Tools > Web Developer).

The page was reloaded, because the character encoding declaration of the HTML document was not found when prescanning the first 1024 bytes of the file. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.

Reloading the page doesn't work properly with the HTTP cache enabled and that causes the content encoding error. I see requests for https://www.longueuil.quebec/ens10/app/ext/suser/test.aspx

I think that the problem is the that page source start with a rather long JavaScript. Firefox is searching for the HTML tag with the content encoding and doesn't find it in the first 1024 bytes as you can see in the Web Console (Firefox/Tools > Web Developer). <blockquote>The page was reloaded, because the character encoding declaration of the HTML document was not found when prescanning the first 1024 bytes of the file. The encoding declaration needs to be moved to be within the first 1024 bytes of the file. </blockquote> Reloading the page doesn't work properly with the HTTP cache enabled and that causes the content encoding error. I see requests for https://www.longueuil.quebec/ens10/app/ext/suser/test.aspx
Размещено

Задавший вопрос

The website is behind Citrix Netscaler, and it is the reason the large javascript code is present at the start of the file (it contains the two calls to test.aspx).

The error in the console is flagged as warning, so I thought it wouldn't be the cause of the content corrupted error.

We'll try to remove that code and see where it goes from there.

Thanks!

The website is behind Citrix Netscaler, and it is the reason the large javascript code is present at the start of the file (it contains the two calls to test.aspx). The error in the console is flagged as warning, so I thought it wouldn't be the cause of the content corrupted error. We'll try to remove that code and see where it goes from there. Thanks!