Stephen Cresswell

I've been looking at this again, and have a couple of issues with it... 1. channel.ch is already public, and not prefixed by an underscore, so hiding it behind a...

Hi @fareed945, If you [search the issues](https://github.com/amqp-node/amqplib/issues/699) you'll see this is typically because you've connected to a server that doesn't use amqp 0.9.1. In some cases people are trying to...

This is what I get from my docker container... ``` Interface: [::], port: 15672, protocol: http, purpose: HTTP API Interface: [::], port: 15692, protocol: http/prometheus, purpose: Prometheus exporter API over...

Hi @fareed945, The most likely thing is still that the client application is connecting to something which isn't communicating using amqp 0.9.1. It looks like Rabbit is listening on all...

Did you get to the bottom of it @fareed945?

``` 2022-08-16 08:39:20.081458+00:00 [error] {bad_header,} ``` That's the start of an HTTP GET request, e.g. ``` GET / HTTP/2 ``` It wasn't made by amqplib

Any update @fareed945?

Thanks @jimmywarting. First glance looks good. I'll review properly shortly.

This looks like a good idea to me, although I think unnecessary if heartbeats or TCP Keep Alive is enabled. Since heartbeats are enabled by default, I would change the...

I've tracked the problem down to how the [frame header is parsed](https://github.com/amqp-node/amqplib/blob/main/lib/frame.js#L47-L48). This is done by a library called [bitsyntax](https://github.com/squaremo/bitsyntax-js), which uses a [parser](https://github.com/squaremo/bitsyntax-js/blob/master/lib/parse.js#L7) generated at build time by the...