remove special exception for 404 (not found) responses
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 15m30s
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 15m30s
These will now be handled just like any other error, allowing downstream to catch and deal with through diagnostics (that did not exist when that code was written)
This commit is contained in:
parent
45d9a369ae
commit
1a03250fbe
1 changed files with 1 additions and 1 deletions
|
|
@ -416,7 +416,7 @@ pub fn Request(comptime request_action: anytype) type {
|
||||||
);
|
);
|
||||||
defer response.deinit();
|
defer response.deinit();
|
||||||
|
|
||||||
if (response.response_code != options.success_http_status and response.response_code != .not_found) {
|
if (response.response_code != options.success_http_status) {
|
||||||
// If the consumer prrovided diagnostics, they are likely handling
|
// If the consumer prrovided diagnostics, they are likely handling
|
||||||
// this error themselves. We'll not spam them with log.err
|
// this error themselves. We'll not spam them with log.err
|
||||||
// output. Note that we may need to add additional information
|
// output. Note that we may need to add additional information
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue