Wireshark · Wireshark-dev: Re: [Wireshark-dev] Still, I can't find the location where the captured data saved

[yami <yamisoe@xxxxxxxxx>]

How to find the cf_read() function is a quiz to you, if you do not know how to do that.

On Mon, Oct 18, 2010 at 2:58 PM, 刘昆 <liukunmeister@xxxxxxxxx> wrote:

于 2010年10月18日 12:43, yami 写道:

packet-http.c is the code for the HTTP dissector only. How captured traffic is saved is a common facility for all protocols.
You may take a look at cf_read() function, which reads captured data from a file. It may different from live capture, but I think it is a good start for you.

On Tue, Oct 12, 2010 at 7:24 PM, 刘昆 <liukunmeister@xxxxxxxxx> wrote:

Still, I can't find the location where the captured data saved.For
example,now I want find which variable save the data captured in the
http protocol.My meaning is the data list at the bottom in the
wireshark.I have searched for the data in the packet-http.c but still
confused.Who can tell me which variable at which function save the data
captured in the http protocol from the network.

And I want to say the header is not really important to me,What I want
to find is the data captured inside the packets.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe

Thank you .However where is the cf_read() fuction.Can you tell me the path of the file which include the cf_read() function?

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe