[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wireshark-dev
Subject:    Re: [Wireshark-dev] HTTP2 headers not dissected
From:       Anders Broman via Wireshark-dev <wireshark-dev () wireshark ! org>
Date:       2020-04-16 6:08:59
Message-ID: AM6PR0702MB3750ADF4A174250AD6923CF995D80 () AM6PR0702MB3750 ! eurprd07 ! prod ! outlook ! com
[Download RAW message or body]

Him
Opened https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16496
/Anders

-----Original Message-----
From: Peter Wu <peter@lekensteyn.nl> 
Sent: den 16 april 2020 00:36
To: Developer support list for Wireshark <wireshark-dev@wireshark.org>
Cc: Anders Broman <anders.broman@ericsson.com>
Subject: Re: [Wireshark-dev] HTTP2 headers not dissected

Hi Anders,

On Wed, Apr 15, 2020 at 03:11:01PM +0000, Anders Broman via Wireshark-dev
wrote:
> It seems like at least in some cases when there is multiple HTTP2 
> streams the header fields are not decoded but if
> 
> Packets belonging to that stream is put in a separate trace file 
> decoding works.

Can you file a bug with an example capture file for the first problematic
case?
--
Kind regards,
Peter Wu
https://lekensteyn.nl

["smime.p7s" (application/pkcs7-signature)]
[Attachment #4 (unknown)]

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

[prev in list] [next in list] [prev in thread] [next in thread]