Hi Peter,

thanks for asking - I just checked (after having to abort looking into it) and
now it seems to be working, at least in the packet decode and the "Decompressed
Header hex view". Using "Follow HTTP2" still gives me gibberish though, but 
maybe
I'm using it wrong or haven't really understood what it's supposed to be doing 
:-)

Cheers,
Jasper

Friday, January 3, 2020, 10:31:30 PM, you wrote:

> Hi Jasper,

> Do you still have an issue? If so, can you check whether TCP reassembly
> is enabled?

> Kind regards,
> Peter

> On Thu, Dec 19, 2019 at 01:51:14PM +0100, Jasper Bongertz wrote:
>> Hi Anders,
>> 
>> you're right, it shows it's included... that means I have a different 
>> problem,
>> but good to know!
>> 
>> Thanks!
>> Jasper
>> 
>> Thursday, December 19, 2019, 1:42:54 PM, you wrote:
>> 
>> > Hi,
>> > On Windows it should be included, check About Wireshark
>> > Regards
>> > Anders
>> 
>> > -----Original Message-----
>> > From: Wireshark-dev <wireshark-dev-boun...@wireshark.org> On Behalf Of 
>> > Jasper 
>> > Bongertz
>> > Sent: den 19 december 2019 13:30
>> > To: wireshark-dev@wireshark.org
>> > Subject: [Wireshark-dev] Brotli decompression
>> 
>> > Hello all,
>> 
>> >   I found this in the release notes of Wireshark 3.2:   "Brotli 
>> > decompression 
>> > support in HTTP/HTTP2 (requires the brotli library)"
>> 
>> >   Sounds great, but I can't seem to find any instructions how to add the 
>> > "brotli
>> >   library" to my Wireshark installation. I guess I need some DLL, but all I
>> >   could find are the Github pages with the source code. Does anyone have a 
>> > good
>> >   instruction set for Wireshark on Windows to enable Brotli?
>> 
>> >   I did a "Follow HTTP2 stream" and got unreadable stuff (decrypted first 
>> > with
>> >   SSLKEYLOG file), so I guess Brotli is  what I need to see the actual 
>> > page 
>> > contents...
>> 
>> > Thanks & cheers,
>> > Jasper
> ___________________________________________________________________________
> 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-requ...@wireshark.org?subject=unsubscribe



jas...@packet-foo.com


___________________________________________________________________________
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-requ...@wireshark.org?subject=unsubscribe

Reply via email to