Re: HTTP not decoded

[M Holt <m.iostreams () gmail com>]

Well, it's not that it's not showing it correctly, it's just showing you the
one packet that is in the capture.
The decode is done properly, but to change the way you are viewing it, you
would need to adjust the setting I mentioned previously.

 -- Mike

On Wed, Nov 3, 2010 at 9:37 AM, Srivats P. <pstavirs () gmail com> wrote:

> Thanks Mike! In other words, if the capture file contained all packets of
> the
> TCP connection, Wireshark would have decoded and shown HTTP correctly -
> right?
>
> Srivats
>
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
> Archives:    http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
>             mailto:wireshark-users-request () wireshark org
> ?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe