libmicrohttpd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libmicrohttpd] How to record messages


From: richard.hedin
Subject: Re: [libmicrohttpd] How to record messages
Date: Tue, 12 Mar 2013 15:13:04 +0000

Hi, Christian. 

I've used wireshark a little bit, but I am far from expert.  Would I have 
trouble filtering out extraneous messages?  Another way to say it, can I tell 
wireshark to give me only messages to and from this particular ip and port? 

               Regards, Rick

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of ext Christian Grothoff
Sent: Tuesday, March 12, 2013 10:09 AM
To: address@hidden
Subject: Re: [libmicrohttpd] How to record messages

On 03/12/2013 03:47 PM, address@hidden wrote:
> Hello all.
> 
> I am using an open source product (MIT Licensed) that consists of a large, 
> complex outer application that communicates with a small, relatively simple 
> inner application.  It's the inner application I am really interested in.  
> It's code looks very strong, but it's documentation is very weak.
> 
> The outer application communicates with the inner engine through a REST 
> interface.  The inner engine uses libmicrohttpd to give it its web activity.  
> I can put the inner engine through its paces by using the outer application.  
> If I could capture the messages that are passed back and forth, I could 
> understand the interface.
> 
> Does libmicrohttpd have some switch I can throw to write all the messages it 
> receives or sends to a file?  Or alternatively, can you tell me where I 
> should insert code to accomplish this?
> 
>                  Regards, Rick
> 
> 

While adding code to do this would certainly be possible, I don't think this is 
the way to do it.

If I were you, I'd use wireshark to grab the HTTP traffic on the network level 
(works also for
loopback!) and you get complete information and a nice viewer on top of it --- 
without writing any code!


Happy hacking!

Christian




reply via email to

[Prev in Thread] Current Thread [Next in Thread]