9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jonadab the Unsightly One <jonadab@bright.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] charon / tcp pasthrough sniffing
Date: Tue,  6 Nov 2001 10:32:05 +0000	[thread overview]
Message-ID: <wk8zdkblfi.fsf@jonadab.homeip.net> (raw)
In-Reply-To: <192275889287.20011026170129@proweb.co.uk>

matt@proweb.co.uk (Matt) writes:

> I'm trying to defeat all the shenanigans on www.genie.co.uk
> they use some tricky techniques to prevent scripting [...]
> Is there some general purpose tcp sniffing technique

Have you already set web browsers aside and spoken directly with the
web server (via HTTP) to see what _exactly_ it's doing?  I've been
known to resort to this (using libwww-perl, but there are other
ways to do the same thing) for particularly intractible websites.


  reply	other threads:[~2001-11-06 10:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-26 15:36 [9fans] Where is vgactl? forsyth
2001-10-26 16:01 ` [9fans] charon / tcp pasthrough sniffing Matt
2001-11-06 10:32   ` Jonadab the Unsightly One [this message]
2001-10-26 16:43 ` [9fans] Where is vgactl? Lucio De Re

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=wk8zdkblfi.fsf@jonadab.homeip.net \
    --to=jonadab@bright.net \
    --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).