Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[Notifier] Add missing charset to content-type for Slack notifier#41211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
OskarStark commentedMay 13, 2021
@nicolas-grekas is this expected behavior of http client? |
OskarStark left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Could you please add a test case to avoid a regression in the future?
and maybe check other transports which are using the 'json' key?
nicolas-grekas commentedMay 13, 2021
Yes it is: |
norkunas commentedMay 13, 2021
Will add a test. I think this is specific only for slack, as by spec json must be in utf-8 so adding charset everywhere shouldn't be required. |
OskarStark commentedMay 13, 2021
Fine thank you 👍🏻 |
OskarStark left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
After a test was added
1de0473 toe642100Comparenorkunas commentedMay 13, 2021
Done ;) |
Nyholm commentedMay 13, 2021
Good catch, thanks Tomas. |
Symfony HttpClient doesn't set charset for the Content-Type header when used with
jsonrequest option so with each response slack includes: