rabbitmq-server
rabbitmq-server copied to clipboard
HTTP API: serve peer port as null for direct (Erlang distribution) connections
It would make more sense as a JSON value: the "traditional" client ephemeral range port is not actually present for those connections are they are not TCP-based in the same way network connections are.
See https://github.com/rabbitmq/rabbitmq-server/issues/3358 for the background.
Thanks Michael. I am not an erlang developer but took some time to look into the code. Shouldn't this be solved more generically closer to the json interface? So that all "undefined" values become null? And all "true" become true.