Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Treat different UNIX destinations like different origins #2069

Open
szmarczak opened this issue Jul 1, 2022 · 0 comments
Open

Treat different UNIX destinations like different origins #2069

szmarczak opened this issue Jul 1, 2022 · 0 comments
Labels
bug Something does not work as it should ✭ help wanted ✭

Comments

@szmarczak
Copy link
Collaborator

It seems that

  1. unix: -> http: works
  2. unix: -> unix: works
  3. http: -> unix: does not work
  4. unix: -> http: -> unix: does not work

2 can leak sensitive headers if the socket path is not the same. For example http://unix/foo:/ -> http://unix/bar:/.

Originally posted by @lpinca in #2047 (comment)

@szmarczak szmarczak added bug Something does not work as it should ✭ help wanted ✭ labels Jul 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something does not work as it should ✭ help wanted ✭
Projects
None yet
Development

No branches or pull requests

1 participant