It seems that
unix:
-> http:
worksunix:
-> unix:
workshttp:
-> unix:
does not workunix:
-> http:
-> unix:
does not work2 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)
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too