Thank you very much Jaap for the inputs and help :)
I will never forget you bro :)
On Wed, Mar 12, 2008 at 2:14 PM, Jaap Keuter <
jaap.keuter@xxxxxxxxx> wrote:
Hi Niel,
First of all, this looks more like a user question, so wireshark-users would
be a better list.
But since we're here lets address it anyway. Wireshark tries to read the TCP
stream, but finds that the HTTP messages are cut short. That is an option of
the capture engine (in order to limit the total capture size, it only stores
the first few octets), or there are multiple fragments that aren't put back
together.
Thanx,
Jaap
niel m wrote:
> Hello Sir/Madam,
>
> Good Day
>
> I am niel, new in using wireshark, I tried to monitor packets and ports
> for a web server.
> My question is... what is the description of this note below;
>
> ---------------------------------------
> 1st situation: <Source IP> <Destination IP> HTTP GET /
> HTTP/1.1[Packet size limited during capture]
> ---------------------------------------
> 2nd situation: <Source IP> <Destination IP> HTTP
> HTTP/1.0 400 Bad Request [Packet size limited during capture]
> ----------------------------------------
>
> Hope you can help me on this.
> I appreciate any help i can get from you guys.
>
>
> Thank you very much
> Niel
>
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev
