From: Tagg McDonald <taggm@dutro.com>
To: netfilter@vger.kernel.org
Subject: Re: Blocking web-based proxy traffic
Date: Wed, 28 Nov 2007 14:41:19 -0700 [thread overview]
Message-ID: <474DE07F.4020903@dutro.com> (raw)
In-Reply-To: <C3731711.2208%jlay@slave-tothe-box.net>
> Interesting idea. I know that when I've captured this proxy traffic I see
> in ASCII "http://" and then whatever proxied site (usually myspace). I was
> thinking maybe a matchstring type thing? Here's a snippet from an
> access.log from a transparent squid proxy, using sureproxy hitting playboy:
>
> 10.1.1.191 - - [28/Nov/2007:12:49:26 -0700] "GET
> http://www.sureproxy.com/nph-index.cgi/011110A/http/www.playboy.com/imx/fron
> tpage/2008-calendars.jpg HTTP/1.1" 200 366
> "http://www.sureproxy.com/nph-index.cgi/011110A/http/www.playboy.com/"
> "Opera/9.24 (Macintosh; Intel Mac OS X; U; en)" TCP_MISS:DIRECT
>
> Does my idea make sense or am I on crack :D
>
> James
If you have a transparent squid proxy in place you can do ACL's and/or
use squidguard or dans guardian.
--
Tagg McDonald
Dutro Company
675 North 600 West
Logan, UT 84321
(435) 752-3921 x146
next prev parent reply other threads:[~2007-11-28 21:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 16:09 Forwarding traffic from public IP to public IP Jason Hawthorne
2007-11-28 16:38 ` Grant Taylor
2007-11-28 17:45 ` Jason Hawthorne
2007-11-28 17:56 ` Blocking web-based proxy traffic James Lay
2007-11-28 19:20 ` Grant Taylor
2007-11-28 20:01 ` James Lay
2007-11-28 20:07 ` Grant Taylor
2007-11-28 20:16 ` James Lay
2007-11-28 20:35 ` Grant Taylor
2007-11-29 10:55 ` Benny Amorsen
2007-11-29 14:24 ` James Lay
2007-11-29 19:21 ` Grant Taylor
2007-11-28 21:41 ` Tagg McDonald [this message]
2007-11-29 1:53 ` dhottinger
2007-11-28 19:17 ` Forwarding traffic from public IP to public IP Grant Taylor
2007-11-28 20:11 ` Jason Hawthorne
2007-11-28 20:42 ` Grant Taylor
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=474DE07F.4020903@dutro.com \
--to=taggm@dutro.com \
--cc=netfilter@vger.kernel.org \
/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