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
The AmazonSqsTransport expects urlencoded user and password (because secrets contains + and /), same for all Mailer/Notifier bridges (decoded by Dsn::fromString) but AmqpTransport does not.
This leads to several issues (reported on Slack) about people not being able to setup the AWS credentials (AWS often provide secret with / or +).
What should be the right behavior? how to setup a AMQP password with special char in DSN? How keeping BC compatibility?