Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Le thread ibilondoloziwe. Nceda ubuze umbuzo omtsha ukuba ufuna uncedo.

Gzip-encoding does not work

  • 4 iimpendulo
  • 2 inale ngxaki
  • 66 views
  • Impendulo yokugqibela ngu JeroenED

JeroenED
JeroenED
more options

For some reason there are some problems with the encoding of internet-files resulting in not loading the particular files.

some more investigation told me there is a problem with gzip-encoding (I'm not sure about deflate). Decompression does not seem to work.

Below you can see the result a website (http://vagrantcloud.com) where the CSS-file failed to load. Obviously, no markup. http://imgur.com/dPuv2S7

If you need some more information about this issue, don't think and just ask in comments. I hope this will be fixed soon.

For some reason there are some problems with the encoding of internet-files resulting in not loading the particular files. some more investigation told me there is a problem with gzip-encoding (I'm not sure about deflate). Decompression does not seem to work. Below you can see the result a website (http://vagrantcloud.com) where the CSS-file failed to load. Obviously, no markup. http://imgur.com/dPuv2S7 If you need some more information about this issue, don't think and just ask in comments. I hope this will be fixed soon.

Isisombulu esikhethiweyo

It seems like a website-specific problem. As a sysadmin I'm using quite a lot sites like vagrantcloud and vagrant. It seems that the server (or CMS-system) does not work well with pipelined requests. Because of this, files to be generated (CSS or JS) are not completely generated when the HTML is send through. This might be the reason why I had this problem only with CSS which could not load (JS is almost never generated by a server)

@jscher2000 I think the mixed content sign is also solved by disabling pipelining.

Funda le mpendulo kwimeko leyo 👍 0

All Replies (4)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

No problems here with Firefox 31.

You can reload web page(s) and bypass the cache to refresh possibly outdated or corrupted files.

  • Hold down the Shift key and left-click the Reload button
  • Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
  • Press "Command + Shift + R" (Mac)
jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Looks okay on my Windows 7 Pro 64-bit system.

I noticed a mixed display content warning in your screen shot (gray ! triangle in the address bar). This sometimes indicates a problem with Firefox's back-forward cache. Does that clear if you reload the page? If not, perhaps one of your add-ons is injecting insecure content. (Not that it would necessarily block a CSS file, but it bears investigation.)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

I hadn't noticed that you used a secure link (only looked at the small image), so I checked that one as well and that is also working

Nothing in the Web Console (Firefox/Tools > Web Developer) log as well.

JeroenED
JeroenED Umnini wombuzo
more options

Isisombululo esiKhethiweyo

It seems like a website-specific problem. As a sysadmin I'm using quite a lot sites like vagrantcloud and vagrant. It seems that the server (or CMS-system) does not work well with pipelined requests. Because of this, files to be generated (CSS or JS) are not completely generated when the HTML is send through. This might be the reason why I had this problem only with CSS which could not load (JS is almost never generated by a server)

@jscher2000 I think the mixed content sign is also solved by disabling pipelining.

Ilungisiwe ngu JeroenED