From: "Steve Simon" <steve.simon@snellwilcox.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] web proxy
Date: Tue, 30 Mar 2004 13:41:51 +0100 [thread overview]
Message-ID: <e67fde5ae6527479091a002cfe831113@snellwilcox.com> (raw)
In-Reply-To: <0057647ac7e4fd07a1dd01ee96d89d03@juice.thebigchoice.com>
On Tue Mar 30 13:33:40 BST 2004, matt@proweb.co.uk wrote:
> thats okay for not seeing ads, however, it could *increase* your bandwidth as hget doesn't use "Accept-Encoding: gzip, deflate, compress", the use of which can reduce your bandwidth requirements for html by around 70%
>
> m
Hmmm, shows how little I know about html.
The idea is to allow me to put my plan9 box on the cablemodem
and proxy the occasional WinNT WWW access for my girlfriend
without paying for a NAT router (the car needs its C service).
-Steve
next prev parent reply other threads:[~2004-03-30 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 12:09 plan9fans
2004-03-30 12:32 ` matt
2004-03-30 12:41 ` Steve Simon [this message]
2004-03-30 13:02 ` matt
2004-03-30 12:36 ` boyd, rounin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e67fde5ae6527479091a002cfe831113@snellwilcox.com \
--to=steve.simon@snellwilcox.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).