Skip to content

Restrict test HTTP egress to loopback#5506

Open
clockwork-labs-bot wants to merge 1 commit into
masterfrom
bot/restrict-http-egress-loopback
Open

Restrict test HTTP egress to loopback#5506
clockwork-labs-bot wants to merge 1 commit into
masterfrom
bot/restrict-http-egress-loopback

Conversation

@clockwork-labs-bot

Copy link
Copy Markdown
Contributor

Description of Changes

Tightens allow_loopback_http_for_tests so it only permits HTTP egress to loopback IP addresses. With the feature enabled, IPv4 addresses outside 127.0.0.0/8 and IPv6 addresses outside ::1 are rejected by the same IP filter used for literal hosts and DNS results.

The production/default behavior is unchanged: loopback remains blocked, private/special-purpose ranges remain blocked, and normal public addresses remain allowed.

API and ABI breaking changes

None.

Expected complexity level and risk

  1. The change is localized to the HTTP egress IP filter and updates existing unit tests for the feature-gated behavior.

Testing

  • LC_ALL=C LANG=C PATH=/Users/clockworklabs/.rustup/toolchains/1.93.0-aarch64-apple-darwin/bin:$PATH /Users/clockworklabs/.rustup/toolchains/1.93.0-aarch64-apple-darwin/bin/cargo test -p spacetimedb-core host::instance_env::test::blocks_ --lib
  • LC_ALL=C LANG=C PATH=/Users/clockworklabs/.rustup/toolchains/1.93.0-aarch64-apple-darwin/bin:$PATH /Users/clockworklabs/.rustup/toolchains/1.93.0-aarch64-apple-darwin/bin/cargo test -p spacetimedb-core --features allow_loopback_http_for_tests host::instance_env::test::blocks_ --lib

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant