clockworklabs / clockworklabs/SpacetimeDB
HTTP API endpoints do not accept `Content-Type`s with `charset` specified
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
POST /v1/database/<…>/call/<…>
Content-Type: application/json; charset=utf-8
{…}
415 Unsupported Media Type
content-type: text/plain; charset=utf-8
Expected request with Content-Type: application/json
This behavior violates RFC 9110's § 8.3.
Meanwhile, SpacetimeDB itself is happy to use charset in its own responses, as shown above.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the HTTP API entry points handling POST requests to /v1/database/<…>/call/<…> and trace how the Content-Type header is validated. Compare the parser's behavior with RFC 9110 §8.3 and verify that application/json with a charset parameter is accepted without regressing unsupported media-type handling.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100