Stream: hapi
Topic: Invalid UTF-8
Grahame Grieve (Oct 30 2018 at 21:10):
@James Agnew if I post a $match operation to the server https://testapp.hospitalitaliano.org.ar/masterfile-federacion-service/fhir which is a HAPI server, the response I get back is
{"resourceType":"OperationOutcome","issue":[{"severity":"error","code":"processing","diagnostics":"El nombre está vacío"}]}
Grahame Grieve (Oct 30 2018 at 21:11):
however: this is not valid UTF-8 encoding. Specifically, it is ANSI not UTF-8. here's the actual bytes that comes back
Grahame Grieve (Oct 30 2018 at 21:11):
Grahame Grieve (Oct 30 2018 at 21:11):
but the header says it is UTF-8
Grahame Grieve (Oct 30 2018 at 21:11):
(as it should)
Grahame Grieve (Nov 02 2018 at 20:59):
@James Agnew ping on this
James Agnew (Nov 05 2018 at 08:42):
@Grahame Grieve Hmm, I am unable to reproduce this locally. Do you have any details around how the error is generated internally? (i.e are they throwing an InvalidRequestException, which would be the recommended way to do this, or are they manually serializing the response, which could explain it..) Or are there any proxies between HAPI and the outside world?
Grahame Grieve (Nov 05 2018 at 20:30):
I don’t know. I’ll chase this up by email
Last updated: Apr 12 2022 at 19:14 UTC
