#3888 closed defect (bug) (invalid)
Translate API not indicating charset
Reported by: | casiepa | Owned by: | |
---|---|---|---|
Milestone: | Priority: | lowest | |
Component: | Translate Site & Plugins | Keywords: | |
Cc: |
Description
Checking https://translate.wordpress.org/api/projects/wp-plugins/akismet/stable with https://jsonformatter.curiousconcept.com/ , it seems that a response header is missing.
The solution is probably in https://stackoverflow.com/questions/39488457/i-dont-understand-whats-wrong-with-this-json
"The server/service exposing that JSON, is not setting the Content-type: application/json; charset=utf-8 in the response header, thus the tool raises the error."
With Chrome developer tools I indeed see that the header is giving the correct content-type but not adding the charset.
Thanks for fixing.
Change History (2)
#2
in reply to:
↑ description
@
5 years ago
- Priority changed from normal to lowest
Replying to casiepa:
Checking https://translate.wordpress.org/api/projects/wp-plugins/akismet/stable with https://jsonformatter.curiousconcept.com/ , it seems that a response header is missing.
The solution is probably in https://stackoverflow.com/questions/39488457/i-dont-understand-whats-wrong-with-this-json
"The server/service exposing that JSON, is not setting the Content-type: application/json; charset=utf-8 in the response header, thus the tool raises the error."
With Chrome developer tools I indeed see that the header is giving the correct content-type but not adding the charset.
Thanks for fixing.
If that one not working Try this JSON Formatter - https://goonlinetools.com/json-formatter/
Thanks for the report! The header is set in GlotPress so it needs to be reported to GlotPress directly.