connect to application server via unix-domain socket #383
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
…0reverse-proxy/test.pl --unix-socket=1` (note: requires an unreleased version of Starlet)
…ce the struct name might be `#define`-ed
10d8efb to
9375d03
Compare
kazuho
added a commit
that referenced
this pull request
Jun 29, 2015
connect to application server via unix-domain socket
Contributor
|
👍 |
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.
Some application servers speaking HTTP/1.1 is capable of listening to an unix-domain socket (which is often faster and easier to operate than TCP sockets).
This PR add to the proxy implementation of H2O the support to connect to such servers.
The URL of such a server is expressed by
http://[unix:/path/to/socket]/path(which loosely conforms to the syntax of URI defined in RFC 3986.obsoletes #51