Using Ziproxy

pkramerruiz · 11-07-2010, 03:12 PM

I had no problem installing Ziproxy, as its in the main packages…
But how to use it?
I mean, so far I could find out, to start it, I musst run:ziproxy --daemon (http://programminglinuxblog.blogspot...-internet.html)

My /etc/ziproxy/ziproxy.conf is full of stuff I've found on internet:

Code:

Address = 0.0.0.0
Port = 9900
NextProxy="127.0.0.1"
NextPort=8118
RunAsUser = "nobody"
RunAsGroup = "nobody"
PreemptNameRes = true
URLReplaceDataCT = "/etc/ziproxy/replace_ct.list"
URLReplaceDataCTList = {"image/jpeg", "image/gif", "image/png", "application/x-shockwave-flash"}
NetdTimeout = 0
TransparentProxy = true
ZiproxyTimeout = 120
MaxSize = 4194304
UseContentLength = false
Compressible = {
        "shockwave", "msword", "foo", "msexcel", "mspowerpoint", "rtf", "postscript",
        "java", "javascript", "staroffice", "vnd.", "futuresplash",
        "asp", "class", "font", "truetype-font", "php", "cgi", "executable",
        "shellscript", "perl", "python", "awk", "dvi"
}
ProcessJPG = true
ProcessPNG = true
ProcessGIF = false
ProcessJS=true
ProcessCSS=true
ProcessHTML=true
ProcessHTML_CSS=true
ProcessHTML_JS=true
ProcessHTML_tags=true
ProcessHTML_text=true
ProcessJP2 = false
ProcessToJP2 = true
ForceOutputNoJP2 = false
AnnounceJP2Capability = true
ImageQuality={-15,20,25,0}
JP2ImageQuality = {5,5,5,5}

But when I run it, and set the Firefox port to:9900 it fails to load any website.

The goal is to compress to the maximum the images, and other stuff that uses too much bandwich (like Opera Turbo).
I really dont care if a picture is full of pixels, or not.

I do not want to use Opera, just to enjoy a fast Internet.
I will not install Midori, Iron, Chrome, eLink or Arora. I want to continue with my usual Firefox and opera. The advantage is that in Firefox, I have NoScript, and other several improvements/extensions, which I cant enjoy in Opera.

I think the fault is, to include four different parameters (Address,Port,NextProxy,NextPort) that are probably for the same thing.

Can someone explain for what is each one, please? And wich is exactly this one I must put into Firefox.

Also had thought that perhaps there is some way to apply the proxy system-wide, not only in the Firefox settings. Maybe by editing the configuration of Networkmanager?

I've also read about Polipo and Varnish-cache… But I think the more accurate solution would be, Ziproxy.

unSpawn · 11-17-2010, 01:43 PM

Quote:

Originally Posted by pkramerruiz

My /etc/ziproxy/ziproxy.conf is full of stuff I've found on internet:

Code:

NextProxy="127.0.0.1"
NextPort=8118

If you don't use ziproxy behind another proxy then those two items should be commented out.

Quote:

Originally Posted by pkramerruiz

My /etc/ziproxy/ziproxy.conf is full of stuff I've found on internet:

Code:

Compressible = {
        "shockwave", "msword", "foo", "msexcel", "mspowerpoint", "rtf", "postscript",
        "java", "javascript", "staroffice", "vnd.", "futuresplash",
        "asp", "class", "font", "truetype-font", "php", "cgi", "executable",
        "shellscript", "perl", "python", "awk", "dvi"
}

...I also wonder if you're going to get much out of this list because 0) some formats can not be compressed (much) more or 1) are already compressed or 2) are not encountered that often. Also most browsers already advertise compression.

Quote:

Originally Posted by pkramerruiz

Can someone explain for what is each one

The ziproxy "README" file already explains what you need.

Quote:

Originally Posted by pkramerruiz

Also had thought that perhaps there is some way to apply the proxy system-wide, not only in the Firefox settings.

Some Desktop Environments include a configuration UI to set proxies (for instance 'gnome-network-preferences') or there may be a command line tool ('gconftool-2 --type int --set /system/http_proxy/port 8118') or else exporting "${protocol}_proxy" variables from a suitable location, say /etc/profile.d/proxy.sh, may work.

Quote:

Originally Posted by pkramerruiz

I've also read about Polipo and Varnish-cache… But I think the more accurate solution would be, Ziproxy.

If you're on a slow line then I wonder if caching requests (beyond the browsers cache) isn't much more effective than compressing things. A client asking for repetitive requests stops at your caching proxy server, which doesn't result in a remote network response, while compressing responses happens at your endpoint, not at the server, and has to be done each and every time.

//NTLB