Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
dpkt
Home
+ new post
About this group
Join this group
Minor changes to http.py, and a error check in pcap.py
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Andrew Brampton  
View profile  
 More options Jan 10 2010, 9:45 am
From: Andrew Brampton <bramp...@gmail.com>
Date: Sun, 10 Jan 2010 06:45:21 -0800 (PST)
Local: Sun, Jan 10 2010 9:45 am
Subject: [patch] Minor changes to http.py, and a error check in pcap.py
Print | Individual message | Show original | Report this message | Find messages by this author
Hi,
I've created three patches that enabled me to decode multiple HTTP
packets in a single TCP stream, including those HTTP packets that are
broken across multiple packets.

[1] The first patch adds a simple validation check to ensure that each
packet within a pcap file is no longer than the declared snaplen. This
was useful for me to figure out I had an invalid pcap file.

[2] The second patch changes the way len(http) works. I had TCP
connections that contained multiple HTTP requests, so I needed to know
accurately how long each HTTP request was, so I modified http to
report this. There might have been a better way of doing this, for
example, parsing a file object into the HTTP unpack, but I didn't want
to change the API too much.

[3] The final patch changes the HTTP class to uncompress gzip encoded
data. This was the reason I started to use dpkt, because I wanted a
"Follow TCP Stream" style view of my connections in plain text (ie not
compressed).

I've also released my little program which outputs the HTTP flows[4].

I hope these patches can be of use. BTW Thanks for creating dpkt, it
has been quite useful!

Andrew

[1] http://me.bramp.net/patches/dpkt-pcap-snaplen.patch
[2] http://me.bramp.net/patches/dpkt-http-len.patch
[3] http://me.bramp.net/patches/dpkt-http-gz.patch
[4] http://bramp.net/blog/follow-http-stream-with-decompression


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google