Apache can decompress gzip'ed files as they're requested!
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Apache can decompress gzip'ed files as they're requested!
Hello,
So Apache can decompress gzip'ed HTML and other files as they're requested. What in the world might be the advantage of this? To save a little bit of hard drive space by compressing, you put so much extra load on the server, don't you? (Because it would have to decompress the file each time before serving it to the client.)
If what I said it correct, then doing so makes no sense because hard drive space can always be added easily and relatively cheaply, while CPU capacity is a more valuable and constrained resource, isn't it?
Are you talking about mod_deflate or mod_gzip for apache?
I think what you are referring to is apache's ability to gzip files on the fly and send it to the browser. That means the whole file is stored on the hard drive. But when it's requested, it's compressed and send to a client (that is, if they support it). This is done to save bandwidth. A lot of bandwidth actually, but at the same time sacrificing cpu and memory load on the server, like you said.
I run a couple of websites out of my own house on a DSL line, which has a very limited upload speed - 300 kilobits. But, by setting up mod_deflate in apache, it makes the website (and server) seem super fast, because it uses less bandwidth.
No, I haven't heard of that before. Where did you read that, I'm curious?
I can't think of any advantage of doing something like that, besides saving disk space. But like you said that would be a horrible waste of cpu and memory usage.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.