<@U0GSLCF1D> Thanks, that seems to work sometimes ...
# ktorj
jtbeckha
10/21/2017, 4:16 PM@ribesg Thanks, that seems to work sometimes but maybe not when the response object goes through gson serialization? Trying to track down the exact problem now.. btw would this work for your issue?
Copy code
call.respond(HttpStatusCode.OK)jtbeckha
10/21/2017, 4:46 PMAh I found it! HttpStatusCode.OK is hardcoded in GsonSupport::renderJsonContent, seems like we just need to pass through any status code set on the response to that function. Wouldn't mind working on an MR for this unless that sounds like a bad idea for some reason
r
ribesg
10/21/2017, 4:52 PMI guess someone supposed that when you respond with data, there was no problem and the status is 200, but that's wrong. Could be 202 or an error payload on a data endpoint.
j
jtbeckha
10/21/2017, 5:12 PMAgreed definitely seems like it should be up to user to set a response code if they want. Looks like GsonSupport has been refactored a bit in the develop branch so might wait for that to get merged in and see if it's fixed
3 Views