net.HTTPClient() drops response body for non-2xx status codes

[Neo Andersson 230]

Hi,

We are developing a QuickApp that communicates with an external REST API server. We have encountered a limitation with the net.HTTPClient() implementation that we would like to report and ask for clarification on.

The problem: When an HTTP request returns a non-2xx status code (e.g. 400 Bad Request), the success callback is triggered correctly with the status code, but resp.data is always empty, even when the server sends a response body with error details.

 

Please login or register to see this code.

 

What the server sends back (confirmed via Postman and other HTTP clients):

 

Please login or register to see this code.

 

 

What we receive in the QuickApp:

• resp.status = 400 ✅
• resp.data = "" ❌ (should contain the error JSON)

Questions:

1. Is this behavior intentional?
2. Is there a way to read the response body for non-2xx responses?
3. Will this be fixed in a future firmware version?

Thank you.

 

 

[jgab 2,642]

I can confirm that behavior, and yes, it's annoying.

[w.rys 7]

You're totally right. I think it should be fixed in the next beta release (5.203), but I cannot promise that yet.