Closed essen closed 8 years ago
The problem comes from a hardcoded {ssl, false} value.
{ssl, false}
SockJS connections local ip/port are wrong, it gives remote ip/port instead. This ticket will also take care of fixing that.
Reported here: https://groups.google.com/forum/#!topic/rabbitmq-users/l3fAt0ZKP2g
I have added a PR against sockjs-erlang which should fixes other related issues.
The problem comes from a hardcoded
{ssl, false}
value.SockJS connections local ip/port are wrong, it gives remote ip/port instead. This ticket will also take care of fixing that.
Reported here: https://groups.google.com/forum/#!topic/rabbitmq-users/l3fAt0ZKP2g