Error variant comments and the requirements table give HTTP 403 or 404 for errors that ExtendDB and DynamoDB answer with HTTP 400

Open Beginner friendly
#1,288 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 5 days

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
backend

Research direction

Read DynamoDbError::status_code in crates/core/src/error/mod.rs alongside the three variant doc comments, then compare them with the error table in docs/design/01-requirements.md. Update the conflicting status descriptions to match the HTTP 400 behavior stated in the issue; done means all three variants and table entries agree with status_code.

Written by the indexing model from the issue text.

Description

DynamoDbError::status_code in crates/core/src/error/mod.rs returns HTTP 400 for UnknownOperationException, IncompleteSignature and UnrecognizedClientException. Its comments say that DynamoDB answers these with 400. The doc comments of the three variants, and the error table of docs/design/01-requirements.md, give another status.

Error Doc comment in crates/core/src/error/mod.rs docs/design/01-requirements.md Status that ExtendDB and DynamoDB send
UnknownOperationException SP-ERR-002: HTTP 404. (line 79) 404 (line 128) 400
IncompleteSignature SP-ERR-002: HTTP 403. (line 89) 403 (line 111) 400
UnrecognizedClientException SP-ERR-002: HTTP 403. (line 92) 403 (line 129) 400

Measured in us-east-1 on 21 Nov 2026, each request twice with the same answer both times, DynamoDB answered HTTP 400 in these cases:

  • IncompleteSignatureException, for DescribeTable requests with a malformed Authorization header.
  • UnrecognizedClientException, for a well-formed header with an unknown access key.
  • UnknownOperationException, for a request with no X-Amz-Target. ExtendDB at f0170bde8 sends the status that status_code returns, HTTP 400.

The fix for #1075 changes the same two lines for MissingAuthenticationToken to 400.

Dominant language
Rust
Stars
517
Forks
60
Avg merge
4d 23h
Merged PRs (30d)
134

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ExtendDB/extenddb

All issues in ExtendDB/extenddb

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.