Skip to content

[Messenger] Inconsitency in DSN user/password encoding #36893

Closed
@jderusse

Description

@jderusse

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?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions