You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we provide an incorrect login or password, the broker closes the connection (without sending the ConnectionCloseFrame, it just terminates the socket connection) and Ridge does not inform about it in any way. I think an exception should be thrown informing about this fact.
Example:
useAmp\Loop;
usePHPinnacle\Ridge\Client;
Loop::run(function () {
$client = Client::create('amqp://user:wrongpass@localhost:5672');
yield $client->connect();
echo"Execution will never get here. Nor will an exception be thrown.";
// (...)
});
When we provide an incorrect login or password, the broker closes the connection (without sending the ConnectionCloseFrame, it just terminates the socket connection) and Ridge does not inform about it in any way. I think an exception should be thrown informing about this fact.
Example:
RabbitMQ logs:
The text was updated successfully, but these errors were encountered: