On 2007-10-19, Sonny <smaniaol@gmail.com> wrote: > > hmm, so it might be GZIPped/BZIP2ed. so how would i parse that if that > is the case? is there a general way to do it. btw, thanks for the info. Sure, pipe the data portion of the packets (in the correct order) through gzip or bzip2. If you control the web server, you can turn off compression if you want to view the data in cleartext instead of uncompressing it first. --keith -- kkeller-usenet@wombat.san-francisco.ca.us (try just my userid to email me) AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt see X- headers for PGP signature information

On 2007-10-19, Sonny <smaniaol@gmail.com> wrote: > On Oct 19, 11:09 am, Keith Keller <kkeller-use...@wombat.san- > francisco.ca.us> wrote: >> >> Sure, pipe the data portion of the packets (in the correct order) >> through gzip or bzip2. If you control the web server, you can turn off >> compression if you want to view the data in cleartext instead of >> uncompressing it first. > > Ok, thanks, i'll try to do that. Btw, here is the code i'm using which > is found in http://everything2.com/index.pl?node_id=1459992. Actually > we're just building a prototype for proof of concept. I'm printing the > payload at the bottom, and on some computers, its encoded/compressed > data we're seeing. What's the best way, let's say, to get the value of > host? Do what I suggested. Since you're writing code, just include the gzip or bzip2 libraries. As I wrote, if you control the webserver, you can turn off compression, which will eliminate a debugging point while you're still developing your code; later you can add compression to test that part of the code. (If you control the client, you can probably turn off compression there, too.) --keith -- kkeller-usenet@wombat.san-francisco.ca.us (try just my userid to email me) AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt see X- headers for PGP signature information