clockworklabs / clockworklabs/SpacetimeDB
Add/expose config to standalone to allow disabling SSRF protections for procedure HTTP requests
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Request from Discord: a user with a standalone deployment wants to make HTTP requests against internal local addresses, but is blocked by our SSRF protection. We have an internal, unstable cargo feature to disable this protection, allow_loopback_http_for_tests. We should figure out some sensible way to expose this at runtime via a config file.
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 by locating the standalone deployment's runtime configuration and the internal allow_loopback_http_for_tests cargo feature that controls SSRF protection. Determine a suitable config-file setting for standalone deployments, then verify that procedure HTTP requests can target internal local addresses when it is enabled and remain protected by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100