Skip to content

API fix for non UTF-8 data

Micael Bergeron requested to merge 35942_api_binary_encoding into master

What does this MR do?

This should fix #35942 (closed) when trying to represent non UTF-8 data in JSON. There are some diff that treated as text when they are binary.

This fix will fake the standard binary message instead of dumping binary data.

Are there points in the code the reviewer needs to double check?

Should I add API level tests for the specific gitlab-test commit? Where are those located?

Why was this MR needed?

Calling the api endpoint caused a 500 error.

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

Edited by Micael Bergeron

Merge request reports