Request handling hardened.
- Security
Method-override headers are rejected
A request carrying X-HTTP-Method-Override (or X-HTTP-Method / X-Method-Override) was executed as the overridden method, so a read could perform a write. These headers are now refused with 400 and METHOD_OVERRIDE_REJECTED. Send the method you mean — the SDK never sent these headers, so no SDK caller is affected.
- Fixed
A body that is not JSON returns 400, not 500
A truncated payload, an XML body or a form-encoded post produced a 500, telling you the server had failed when the request was simply malformed. These now return 400 with INVALID_JSON.
- Fixed
Page size is enforced instead of forwarded
count is now clamped to the documented range (default 20, max 100) and a non-numeric cursor starts from the beginning, rather than being passed through and rejected further down.
- Changed
Error messages no longer carry internal detail
Upstream errors were surfaced verbatim, which exposed infrastructure naming in ordinary 400 responses. Messages are now sanitized at the boundary — the part that tells you what to fix is kept, the rest stays in our logs.