[Cache][DependencyInjection][Lock][Mailer][Messenger][Notifier][Translation] Url decode username and passwords from parse_url() results
#53320
Conversation
|
And again a DSN component would help us across the whole codebase I know this was discussed quite often in the past. Anything changed your mind @nicolas-grekas ? cc @Nyholm |
|
All this makes me think we need a working url parser... (a dsn component is another story.) |
|
To be reusable in a dedicated component ofc, but as this is util and no "domain", I don't know either 🤷♂️ but it sounds good 👍 |
|
Maybe this UrlParser could belong to HttpFoundation? If this is something that could happen, I'll gladly implement this and leverage it in the numerous DSN parsing processes the codebase counts. |
0a90d41 to
1c0fbf2
Compare
|
Rebased to 5.4 to make it a bug fix. I'll have a look at what can be done with some UrlParser/DsnParser to have a global logic over every DSN parsing |
1c0fbf2 to
1f2b2c1
Compare
…lation] Url decode username and passwords from `parse_url()` results
1f2b2c1 to
f0292f2
Compare
|
Thank you @alexandre-daubois. |
Following #52758 (review)
I guess this doesn't an entry in the changelog, does it? I replaced
urldecodebyrawurldecodeand$parsedDsnby$params, as latest updates to the code used the latter.