Joomla! Forum - community, help and support

Hi,

I have a question.

While i've found out apache compresses all my websites hosted on my server with gzip (whatismyip.com's http compression testing tool) i've had joomla gzip compression enabled, but experienced http error 330 from time to time accessing the site. I've read somewhere that could be due to double compression done on the site. Is that correct? is the joomla gzip compression option in general server settings seperate from apaches gzip compression? (which would really mean two compressions are done over the files served to client and generate this error)
the interesting thing was that once i refreshed the site after getting the error 330, the site loaded, is that reasonable? can somebody explain why if it is?

thanks a lot for your help in advance,

Speedy-Software

btw. i'm using joomla 1.7 for this website.

speedy-software wrote:btw. i'm using joomla 1.7 for this website.

Welcome to Joomla forum!

Please upgrade always to the latest Joomla version within the same series before trying to solve errors with an older version. Possible bugs might have been solved in the meantime, and it's a waste of time trying to solve issues that are caused because of non-updated software...

Joomla 1.6 + 1.7 where short term support versions and are no longer supported.
Joomla 2.5 is the long term support version in the same series...
The latest version in the 2.5 series is Joomla 2.5.8: http://www.joomla.org/download.html

Ya they're different.

You can compress content using php w/in scripts so PHP can compress pages and a lot of third party extensions can compress your scripts for you. This is good b/c if you're on shared hosting without the ability, this is your only option.

Apache has modules you can install like mod_gzip (for apache versions under 2) and mod_deflate (for apache versions 2+). This will compress all of your outgoing content the client requests based on rules setup (js, css, html, all, none, what compression level, etc.).

you can configure these modules in .htaccess (per directory) or in httpd.conf for the entire server. The existence of .htaccess if allowed overrides will alter the base settings in httpd.conf.

So if you are double compressing, turn of joomla's compression because you're already compressing the content and more most likely. So when the client goes to uncompress the content, it gets the next layer of compressed content from double compression and doesn't know what to do with it. It could in fact be garbage at that point if it's compressed twice...not sure.