32 lines
1.2 KiB
Plaintext
32 lines
1.2 KiB
Plaintext
|
From: jeremy at cnri.reston.va.us (Jeremy Hylton)
|
||
|
|
Date: Sat, 10 Apr 1999 14:40:19 -0400 (EDT)
|
||
|
|
Subject: Internet Robot
|
||
|
|
In-Reply-To: <7emldl$rh9$1@nnrp1.dejanews.com>
|
||
|
|
References: <7ehe9m$hbs$1@nnrp1.dejanews.com>
|
||
|
|
<m3emluaecc.fsf@solo.david-steuber.com>
|
||
|
|
<7emldl$rh9$1@nnrp1.dejanews.com>
|
||
|
|
Message-ID: <14095.39355.48967.900033@bitdiddle.cnri.reston.va.us>
|
||
|
|
X-UID: 75
|
||
|
|
|
||
|
|
How are you generating your HTTP requests? httplib or urllib? IN
|
||
|
|
either case, you ought to be able to get Python to print out some
|
||
|
|
debugging information, which will be much more useful than doing
|
||
|
|
something with a packet capture tool. There's nothing fancy going on
|
||
|
|
at the packet level that you need to look at -- just the data that's
|
||
|
|
coming back over the socket. One of the easiest ways to do that is
|
||
|
|
with the set_debuglevel method on an HTTP object.
|
||
|
|
|
||
|
|
But your question probably has an even easier answer: What kind of
|
||
|
|
authentication is the server doing? Python supports HTTP Basic
|
||
|
|
authentication with urllib, and I've gotting a working implementation
|
||
|
|
of Digest authentication that should be ready for release any day now.
|
||
|
|
|
||
|
|
The authentication support is not well documented (if it's documented
|
||
|
|
at all), so you'll have to look at the code.
|
||
|
|
|
||
|
|
Jeremy
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|