search

IBM / IBM-QRadar-Universal-Cloud-REST-API

These workflows are provided for sample usage, new submissions and updates from the community, and are NOT supported by IBM.
44 stars 89 forks source link

When no charset is included in the Content-Type CallEndpoint response header - ISO_8859_1 is used instead of UTF-8 #246

Open ChrisCollinsIBM opened 2 weeks ago

ChrisCollinsIBM commented 2 weeks ago

Discussed in https://github.com/IBM/IBM-QRadar-Universal-Cloud-REST-API/discussions/228

Originally posted by **JiaChee** March 20, 2024 Hello Team, Is there any doc available to show Universal Cloud REST API support chinese characters via POST method? For GET method, it is able to capture Chinese characters in good conditions. @ChrisCollinsIBM
ChrisCollinsIBM commented 2 weeks ago

Details here: https://github.com/IBM/IBM-QRadar-Universal-Cloud-REST-API/discussions/228#discussioncomment-9755610

TLDR: some unicode characters will be mangled if charset isn't included in the HTTP response.

Next RPM release will include a change to UTF-8 as the default if not otherwise specified.