feat: clear no-proxy envs for child process#182
Merged
evgeniy-scherbina merged 2 commits intomainfrom Feb 20, 2026
Merged
Conversation
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
1 participant
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.
Summary
In Landjail, corporate envs often set
no_proxy(e.g..internal.cloud). The target then bypasses Boundary’s proxy for those hosts and connects directly; Landlock blocks those connections.Clear
no_proxyandNO_PROXYin the env we pass to the child (and thus the target) so all traffic goes through Boundary’s proxy.Changes
getEnvsForTargetProcess(), setno_proxy=""andNO_PROXY=""in the merge map so they override the parent’s values.Parent env is unchanged; only the child and target get the cleared proxy-bypass vars.