On Thursday 04 December 2003 00:56, Felix Karpfen wrote: > * Juraj Variny <[EMAIL PROTECTED]> [04.12.03 06:56]: > > it depends on the remote server whether he uses to send compressed > > responses or not. Ziproxy can compress all responses. > > And with that advice all my previous confusions return. > > README.compress - assuming that I have understood what it says - > indicates that, provided that the server uses to HTTP 1.1 protocol, > files are sent in compressed format if the receiving browser can handle > that format. And WWWOFFLE-2.8, with zlib installed, presumably can.
But many servers doesn't. Compression isn't built into Apache web server, an special module (mod_gzip) must be used. Many admins forget it to set up. IMHO running wwwoffled with debugging output enabled could reveal how many servers just don't return compressed response despite being asked by wwwoffle. > So if the time of WWWOFFLE fetches can be halved, what points to > "127.0.01", what listens at port 8080 and what port entry - referring to > ziproxy - goes into /etc/services? This file is bound to (x)inetd and I find it quite complicated to explain here how. Just add type=UNLISTED into xinetd configuration file for ziproxy and it won't care for /etc/services. I didn't understood rest of your question. Try following the wwwoffle-privoxy-internet setup, with only difference that ziproxy won't be at localhost like privoxy, but somewhere on other end of the line. > Finally, ziproxy give just too many choices - use with xinetd, with > inetd or (from the commandline) with netd. So, which? Use either inetd or xinetd (whatever is installed) when you're admin on the server where you're going to use ziproxy. When you have only an normal user account, use netd. There isn't any other difference in functionality. Just choose one. Just keep asking. I know ziproxy setup with wwwoffle isn't trivial for linux+networking beginners, maybe there could be made an "ziproxy-wwwoffled mini-HOWTO" from this. Juraj
