Re: Kafka wire protocol and Wireshark capture don't seem to align.

I read the code again. In `ApiVersionsResponseData._write()`, there is a check of the version. If >=3, the API keys array is pre-prended by one byte that contains the length of the following array. Else, it is an INT32 that contains the length of the following array. So, the 0x3c in my case is the

Re: Kafka wire protocol and Wireshark capture don't seem to align.

There used to be a kafka dissector that I thought was shipped with Wireshark - does that decode this properly? I wasn’t certain if you were trying to decode it yourself or if the kafka dissector wasn’t working. I wrote something up here about using the dissector, but it’s been almost a decade

Re: Kafka wire protocol and Wireshark capture don't seem to align.

The correlation ID is in the response **header**. On Sun, Oct 27, 2024 at 10:36 PM Ömer Şiar Baysal wrote: > Hi, > > Could not able to find correlationID response for the Apiversions API, did > you mean Produce API? > > Maybe it is throttleTimeSize ? > > > https://github.com/a0x8o/kafka/blob/54e

Re: Kafka wire protocol and Wireshark capture don't seem to align.

Hi, Could not able to find correlationID response for the Apiversions API, did you mean Produce API? Maybe it is throttleTimeSize ? https://github.com/a0x8o/kafka/blob/54eff6af115ee647f60129f2ce6a044cb17215d0/core/src/main/scala/kafka/api/ProducerResponse.scala#L68 On Sun, Oct 27, 2024, 17:42 C