[Mr444-dev]

Summary

• Treat X-ClickHouse-Exception-Code as a server error even when progress headers leave the HTTP status at 200.
• Preserve the server error code and body, and report an error if the response body is empty.
• Add regression coverage for InsertBinaryAsync and a changelog fragment.

Fixes #705

Validation

• Targeted .NET 9 tests: 3 passed, 0 failed. The test fixture setup used a local HTTP stub; the regression tests exercise a fake HTTP response.
• dotnet run scripts/changelog.cs -- --check passed.

---

Note

Medium Risk
Central HTTP error handling changed for all callers of HandleError, including inserts and queries; behavior is more strict but aligns with server semantics and prevents silent insert failures.

Overview
Fixes a case where binary inserts (and other operations using HandleError) could succeed even though ClickHouse failed after streaming progress headers—the HTTP status stays 200 while X-ClickHouse-Exception-Code carries the real failure.

HandleError now treats any response with that header as an error, not only non-2xx statuses. When the body is non-empty, the thrown ClickHouseServerException uses the header value as ErrorCode when present; empty-body paths get clearer messaging for “exception reported with HTTP 200.”

Tests add InsertBinaryAsync regression coverage and extend the empty-body + header test to HttpStatusCode.OK as well as 503. Changelog fragment for #705.

^{Reviewed by Cursor Bugbot for commit 40850ae. Bugbot is set up for automated code reviews on this repo. Configure here.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Reviewed by Cursor Bugbot for commit 2044fba. Configure here.}

[Mr444-dev]

Removed the generated changelog placeholder so the fragment now contains only the release note for #705. dotnet run scripts/changelog.cs -- --check passes.