[GLUG-chat] Re: gzip proxy

["Adrian X" <xadrianx@xxxxxxxxx>]

Continuing the top posting

What I ended up doing:

Install squid on the remote server and configure as it should be.
Setup a local server to tunnel http over ssh connecting to the proxy.

For the tunneling:

$ ssh -C -g -LXXXX:proxy.server:YYYY user@xxxxxxxxxxxx

The -C provides the compression
-g allows other to connect to the proxy
-L bind sockets
XXXX = local port
YYYY = proxy port on remote server

Then set the client machines to use the local server as the proxy.

A little more of a work-a-round than a straight gzip proxy but it has
a few benifits (everything is compressed, secure up to the proxy).



On 3/20/06, Raymond Leach <raymondl@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> Since we're all top posting today ...
>
> See this site:
> http://www.swelltech.com/squidgzip/
>
>
> On Monday 20 March 2006 14:07, Adrian X wrote to Glug Chat:
> > Aside from Apache and rabbIT, there is a proxy called ziproxy which
> > goes beyond the html compression and adds image compression to it's
> > list of features.
> >
> > I'm not too keen on installing Apache just for this proxy and have
> > given up on getting lighttpd to act as a gzip proxy. I'll try this on
> > the laptop before I have a go on the server.
> >
> > On 3/20/06, Brett Geer (DHL ZA) <Brett.Geer@xxxxxxx> wrote:
> > > If anyone's got HTTP/1.1 support patched into squid, please let me
> > > know how you got that right. I have a use for it.
> > >
> > > Personally I think that using Apache is an absolute cludge as you
> > > don't get the fine granularity of control that squid gives you and
> > > even if you had the Apache server do the actual fetch and hand it
> > > to a squid proxy, in between the client and the squid host they're
> > > still stick with 1.0, which defeats it. Unless you have squid do
> > > the fetch and Apache hand it back to the client, that might work
> > > but if your client is sitting on your LAN and so is your squid box,
> > > you don't get any gain.
> > >
> > > I do see that support for 1.1 isn't too complete in the browsers,
> > > as per my previous post where I showed my exclusion list. Thats
> > > damn annoying because you never know what they're going to screw up
> > > next.
> > >
> > > brett
> > >
> > > -----Original Message-----
> > > From: Gustav H Meyer [mailto:gustav@xxxxxxxxxxx]
> > > Sent: 20 March 2006 11:47
> > > To: Brett Geer (DHL ZA)
> > > Cc: Glug Chat
> > > Subject: Re: [GLUG-chat] Re: gzip proxy
> > >
> > >
> > > Hi Brett,
> > >
> > > >> On 17/03/06 16:52, Brett Geer (DHL ZA) wrote:
> > > >>> Squid isn't going to do it, HTTP/1.1 is on the cards for
> > > >>> later releases
> > >
> > > It seems that this issue has been debated at length in many
> > > different places but I can't really find any recent discussions
> > > about it. So here's my basic question.
> > >
> > > Is it not advantageous to have specifically this feature available
> > > on proxy servers of these days? We also use squid on our side and I
> > > should probably be asking this question on the squid lists but I'm
> > > just testing the waters on this list because I know there's some
> > > experienced guys in here and maybe you'll be able to give some more
> > > pointers before I go to the squid experts.
> > >
> > > It seems that version 3.0 of squid will support this but this
> > > release (as far as I can see) is still some way off. Is there not a
> > > way that one can patch the current stable squid to include
> > > compression? Anybody on this list done this?
> > >
> > > Background reading:
> > > http://www.w3.org/Protocols/HTTP/Performance/#Compression
> > > http://www.squid-cache.org/mail-archive/squid-dev/200208/0240.html
> > >
> > > >>> but apache with mod_gzip, sorted.
> > > >
> > > > On 17/03/06 17:30, Gustav wrote:
> > > >> This put's a little spanner in the works because many proxies
> > > >> out there are based on squid. It basically means that any
> > > >> client going via a squid based proxy will not see the benefits
> > > >> of compressions. Right?
> > >
> > > On 20/03/06 09:21, Brett Geer (DHL ZA) wrote:
> > > > Correct. Even if you enable the 'Use HTTP/1.1 thru proxies' (IE
> > > > option, Netscape does it by default)
> > >
> > > Firefox also does it by default as far as I can see but there's no
> > > point if the proxy does not support it.
> > >
> > > Regards,
> > > Gustav H Meyer
> > >
> > >
> > >
> > >
> > >
> > > ---
> > > To unsubscribe: send the line "unsubscribe glug-chat" in the
> > > subject of a mail to "glug-chat-request@xxxxxxxxxxxx".
> > > Problems? Email "glug-chat-admins@xxxxxxxxxxxx". Archives are at
> > > http://www.linux.org.za/Lists-Archives/
> >
> > ---
> > To unsubscribe: send the line "unsubscribe glug-chat" in the
> > subject of a mail to "glug-chat-request@xxxxxxxxxxxx".
> > Problems? Email "glug-chat-admins@xxxxxxxxxxxx". Archives are at
> > http://www.linux.org.za/Lists-Archives/
>
> --
> --
> Raymond Leach <raymondl@xxxxxxxxxxxxxxxxxxxxxx>
> Network Support Specialist
> http://www.knowledgefactory.co.za
> "lynx -source http://www.rchq.co.za/raymondl.asc | gpg --import"
> Key fingerprint = 7209 A695 9EE0 E971 A9AD  00EE 8757 EE47 F06F FB28
> --
>
>
> ------------------------------------------------------------------------------------------
> This e-mail was checked by the e-Sweeper Service.
> For more information visit our website, Clearswift Corporation e-Sweeper :
> http://www.mimesweeper.com/products/esweeper/
> ------------------------------------------------------------------------------------------
>
>
---
To unsubscribe: send the line "unsubscribe glug-chat" in the
subject of a mail to "glug-chat-request@xxxxxxxxxxxx".
Problems? Email "glug-chat-admins@xxxxxxxxxxxx". Archives are at
http://www.linux.org.za/Lists-Archives/