Or you can use tcpflow:
http://www.entropy.ch/software/macosx/#tcpflow
and you can see the content of tcp packet.
I am using the 0.21 package and it work well on 10.3 and 10.4
Don't forget the -c flag to see content on the console.

Alain


Le 27 déc. 05, à 21:57, John M McIntosh a écrit :

> I think if you look at the man page for TCPDUMP you'll find it can  
> dump the contents of the tcp packets, versus the headers, then you can  
> see exactly what the browser is
> sending and getting.
>
> On 27-Dec-05, at 10:30 AM, Michael Rueger wrote:
>
>> Nevin Pratt wrote:
>>
>>> As far as I can tell, that doesn't tell me anything about why the  
>>> Microsoft IIS server at "testing.shippingapis.com" is treating the  
>>> two requests differently-- why it works fine when my browser is the  
>>> client, but returns a "400 Bad Request" error when Squeak is the  
>>> client.
>>
>> You will need to look at what the browsers are sending.
>> One way would be to open a listening socket in squeak on port 80 and  
>> then connect to it with your browser with a url like
>> http://localhost/ShippingAPITest.dll?API=Verify&XML=<AddressVa ...etc
>>
>> Or even before that look at how squeak actually parses the URL.
>>
>> Michael
>>
>
> --
> ======================================================================= 
> ====
> John M. McIntosh <johnmci at smalltalkconsulting.com> 1-800-477-2659
> Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
> ======================================================================= 
> ====
>
>