Merged
Conversation
When proxying to a Unix domain socket upstream, write a PROXY v1 header before copy_bidirectional so the backend can recover the real client IP and port (which are otherwise invisible over UDS). Format: PROXY TCP4/TCP6 <src-ip> <dst-ip> <src-port> 0\r\n TCP upstreams are unaffected. Upgrading to v2 (for TLS metadata such as client cert CN) is the natural next step when needed. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Update package name in root package.json, all npm sub-packages, and the native addon loader in proxy.ts. Add license field to Cargo.toml. Replace the LICENSE file with the Elastic License 2.0 text. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
2 participants
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.
Pairs with HarperFast/harper@52b9844
Send PROXY protocol v1 header to UDS upstreams
When proxying to a Unix domain socket upstream, write a PROXY v1 header
before copy_bidirectional so the backend can recover the real client IP
and port (which are otherwise invisible over UDS).
Format: PROXY TCP4/TCP6 0\r\n
TCP upstreams are unaffected. Upgrading to v2 (for TLS metadata such as
client cert CN) is the natural next step when needed.