Weblogs.com Not Using HTTP Compression

Ummm, this one floored me. If Weblogs.com wants to reduce their traffic, turn on mod_deflate in Apache 2.0.

HTTP/1.1 200 OK
Date: Fri, 02 Sep 2005 14:13:10 GMT
Server: Apache/2.0.46 (Red Hat)
Last-Modified: Fri, 02 Sep 2005 14:09:54 GMT
ETag: "ac0b3-3559d-840c3080"
Accept-Ranges: bytes
Content-Length: 218525
Connection: close
Content-Type: text/html; charset=UTF-8

I know it won’t solve everything, but it’s a start.

Categories: Uncategorized

6 Comments

  1. Unfortunately, most clients don’t support it, so it really wouldn’t make much of a difference.

  2. AU CONTRAIRE!
    All major browsers, and most recent proxy servers do handle compressed content very well.
    This myth has lasted since the Netscape days, and was solidified by a broken version of MSIE many years ago.
    IT IS UNTRUE!
    We busted a major Canadian bank that was not allowing any version of MSIE to be sent compressed content. But they happily sent compressed content to Firefox and Opera.
    Content Compression works. Do it.

  3. Unfortunately, the load at Weblogs.com is not browsers, it’s people writing PHP using HTTP clients that don’t.

  4. Unfortunately, most clients don’t support it, so it really wouldn’t make much of a difference.

  5. All major browsers, and most recent proxy servers do handle compressed content very well. This myth has lasted since the Netscape days, and was solidified by a broken version of MSIE many years ago.IT IS UNTRUE!We busted a major Canadian bank that was not allowing any version of MSIE to be sent compressed content. But they happily sent compressed content to Firefox and Opera.Content Compression works. Do it.

  6. Unfortunately, the load at Weblogs.com is not browsers, it’s people writing PHP using HTTP clients that don’t.

Leave a Reply

Your email address will not be published.

5 + eighteen =

Copyright © 2022 Performance Zen

Theme by Anders NorenUp ↑