Closed wraithan closed 8 years ago
I've seen some libraries explicitly handle connection.close
during connection.open
phase to indicate invalid vhost.
@wraithan thank you.
Yeah, would love to see the vhost thing handled a bit better. We saw in the examples that you use IP address and had an extra slash for vhost when we were starting to use the library, we tested a bit to see which one was causing the issue.
Might be cool to just default to /
if you don't specify. That is how many libraries work (like defaulting to using 5672 as the port). But I understand if you prefer to not have many defaults and lean toward always being explicit.
Without the extra
/
in the example it tries to connect without a vhost which causes mysteriousConnectionReset
errors orProtocol("Unexpected method frame: connection.close, expected: connection.open-ok")
depending on configuration and OS.