CODEWITHSUNDEEP
compressionbandwidthhttp-compression
Haroldo
Haroldo

Reputation: 37377

Any reasons not to gzip documents delivered via HTTP?

I remember someone telling me that gzipped content is not cached on some browsers? is this true?

Are there any other reasons why I shouldn't gzip my content (pages, javascript and css files) with htaccess?

Upvotes: 2

Views: 297

Answers (4)

Glen Little
Glen Little

Reputation: 7128

If you need to stream the content of a page, or want to use Response.Flush, then you can't use compression/gzip.

Upvotes: -1

Marcelo Cantos
Marcelo Cantos

Reputation: 185902

If you are delivering mostly .gz files, then obviously you don't want to gzip them. Otherwise it's probably a good idea, especially for cache-able content. I have never heard of caches not working with gzipped content.

Upvotes: 1

Ben Everard
Ben Everard

Reputation: 13804

The other reason is it obviously increase CPU load, but whether this is a problem depends on your content type and your traffic.

If you are going to use GZip from with .htaccess, be sure to wrap it in a condition whereby it only executed of the mod_gzip module exists, this will make the site / app more portable if moving it to another server.

If you opt to use .htaccess GZipped content the browser will receive compressed content if it supports it, or received the normal uncompressed version if it doesn't

Upvotes: 3

AutomatedTester
AutomatedTester

Reputation: 22418

I think you need to handle both GZipped and not gzipped data since IE6 and GZipping do not live together nicely.

Otherwise I cant think of an issue

Upvotes: 0

Related Questions