strings should be only mangled when the response type is JSON

[devkral]

Checklist

• The code has 100% test coverage.
• The documentation was properly created or updated (if applicable) following the correct guidelines and appropriate language.
• I branched out from the latest main or is a sub-branch.

Summary or description

strings should be only mangled when the response type is JSON
Why?

Otherwise when media_type is e.g. text/html, all apostrophes are escaped. I think this is unexpected.
@tarsil what do you think?

[tarsil]

Checklist

• The code has 100% test coverage.
• The documentation was properly created or updated (if applicable) following the correct guidelines and appropriate language.
• I branched out from the latest main or is a sub-branch.

Summary or description

strings should be only mangled when the response type is JSON Why?

Otherwise when media_type is e.g. text/html, all apostrophes are escaped. I think this is unexpected. @tarsil what do you think?

I agree. Somehow that was missed. We can't escape if it's HTML. We introduced this recently in some of the clean up.