mod_gzip have anything to do with garbage pages returning to the users at times?

for the last 6 months of using mod_gzip, never heard any of my customer complain about it ... What garbage pages are you referring about?

cheers,
:beer:

Does gzip affect any of the HTML. I wish to know more about it because our tech guy said he installed it for us and sort of explain what it does.

Mod_Gzip doesn't do anything to the HTML. It just compresses the files before it leaves the server, kind of like what winzip does to a text file. It compresses on the server before it's sent out, then uncompressed by the browser. If the browser does not support gzip (most new ones do from 1998+ I think), the server will not send it compressed.

Quite an amazing little tool. I haven't had any problems with it at all. (Knock on wood).

likely your referring to a php script? and it returns garbage characters? thats because the php file requires Zend Optimizer to read the file which was encoded in zend encoder..thats if this relates to a php file rather then html files... :)

If you get tons of http requests and big html files using mod_gzip will cause the system resources to go up and of cource the server load.

So long as your server has enough resources to run modgzip (and realize, it will run on every html/text/script file if told to do so) then you should have no problems. You may have a few log files generated as people close pages midway or if the resources get low and gzip is unable to run but baiscally you should be fine.

If your serve has a high load average (you should upgrade) but you can also set several options in modgzip to lower the compressionr atio, not to comrpess under X load and so forth. You should make sure to do this to help protect your server it its time of need.

Mod gzip can easily save high text/ html sites 50% or more on their monthly bandwidth ussage. There are no real downsides as older browsers are given normal pages. Make sure not to run it on images though as your load will go way up (since images are normally the most common file loaded) and many netscape users have problems with the compressed images!

Originally posted by netsolutions
Does gzip affect any of the HTML. I wish to know more about it because our tech guy said he installed it for us and sort of explain what it does.

All I know is I got an email from a client saying that some of there viewers were getting "garbled" pages. He suggested that it would be the mod_gzip, but im not sure ? wierd.

My load doesnt normally go any higher than .15 and the ram is usually sitting at around 60% no higher.

The only way that would happen is if modgzip was ignoring user gents (which it would only do if someone changed the setup/ code) or if it was installed incorrectly. Other then that, it should have no problems as it only works on browsers that understand it.

Hi!
Given below is a brief description of mod_gzip. Please note that it is taken from their site.

mod_gzip is an Internet Content Acceleration module for the popular
Apache Web Server.
It is a complete working version of the product fully tested and ready to fulfill your Internet Acceleration needs. mod_gzip uses the well established and publicly available IETF( Internet Engineering Task Force ) Content-Encoding standards in conjunction with publicy available GZIP
compression libraries such as ZLIB
( Copyright © 1995-1998 Jean-loup Gailly
and Mark Adler ) to deliver dynamically compressed content 'on the fly' to any browser or user-agent that is capable of receiving it. It is a software based solution that runs perfectly in conjunction with any Apache Web Server on both UNIX and Win32 platforms. No additional client side software is required to use this product.
mod_gzip does not require ANY software to be installed on the client side. There is no accompanying 'Plug-in' or 'Client Proxy' of any kind. All you need is your current HTTP 1.1 compliant browser.

All modern browsers released since early 1999 are already capable of receiving
compressed Internet content via standard
IETF Content Encoding if they are HTTP 1.1 compliant. If standard IETF Content Encoding is what you need to accelerate your Apache Web Server, reduce your CPU load, and deliver 75-80 percent less data with no loss of content to your users at all times then look no farther. HSC's mod_gzip is all that you need. mod_gzip is available for all Windows and UNIX based platforms supported by the Apache Web Server


You could try disabling mod_gzip and see if the problem still exists.

Have a great day :)

Regards
amar

Originally posted by Palm
If you get tons of http requests and big html files using mod_gzip will cause the system resources to go up and of cource the server load.
Actually it's supposed to decrease server load. :) It caches compressed files and when people request the same file again, it has the file already compressed and zips it out to the user. I'm not sure, but I think this only works on static files. Dynamic ones have to be re-compressed (and again, it hardly loads the server, even on _heavily_ used sites).

Don't compress things like .jpg and .zip files. They are already compressed and will just make your server work harder than it should. If you configure mod_gzip correctly, it should work perfectly fine on very heavily used sites.

The garbage is prolly from css or .js files - exclude these in your config and off you go.

This is because it changes from ascii to binary, so the line breaks get garbled into unrecognized characters, which is why you should exclude css and js files.

mod_gzip is a very usefull module. We've been using it for almost a year now and never had any complaints. Looking at the logs, one of our HTML files on 50KB got gziped down to < 4KB. If we say a modem user is loading that page, it will take about 1 sec instead of 12 seconds (assuming they get 5kb/s download). You should exclude images, .css, .js and such for better preformance.