docs: note firewall accept-first behavior on internet access page#233
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
There was a problem hiding this comment.
Pull request overview
Adds a warning callout to the Internet access docs clarifying that, due to firewall routing, TCP connections from inside the sandbox can appear to succeed even when blocked by denyOut rules, and recommends checking for an application-level response to confirm traffic flow.
Changes:
- Inserts a
<Warning>block indocs/sandbox/internet-access.mdxexplaining the accept-first TCP behavior. - Advises verifying connectivity via application-level signals (HTTP status, TLS handshake, etc.).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
sitole
approved these changes
Jun 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a warning to the Internet access page explaining that, due to how outbound TCP traffic is routed to the egress firewall, a TCP connection from inside the sandbox can appear to succeed even when the destination is denied by
denyOutrules — no packets actually reach the destination.Recommends checking for an application-level response (HTTP status, TLS handshake, etc.) to verify that traffic is actually flowing.
Context: internal thread clarifying that the firewall must accept the connection first and use a syscall to retrieve the original destination IP before applying egress rules.