REST consume: gracefully handle BOM

Not right now

I've noticed that some webservices (notably MS Graph when returning an error) put a UTF-8 BOM (byte order mark) before the actual JSON payload. The Platform cannot handle this currently, and a OnAfterResponse is needed to strip it. It'd be nice if the Platform could do that, as BOMs should be ignored.

Created on 1 Oct 2016
Comments (1)
Changed the status to
Not right now

Hi Kilian,

Sorry for the late reply, but we are not planning on delivering this in the near future.

Although this totally makes sense, with the upcoming new features that we have in mind and since it's possible to handle this situation in the OnAfterResponse, we currently don't have plans to tackle this in the near future.

Nonetheless, thank you very much for your idea and keep it coming.

If you believe we missed some context that would change our perception about it, please give us more details about why you would need this and for what is the use case.