Browse HTTP over AF_UNIX
up vote
0
down vote
favorite
Anyone know of a browser that supports this?
I've written a service using NodeJS and express and I'd like to limit its use to the local user 0o700 and I figured the best way to do that is using a UNIX domain socket.
Only question remains: how do I communicate with it from a browser window? Most browsers don't seem to support something along the lines of a http+unix://... scheme.
The communication needn't be two-way but that would be nice and I've considered the following:
- Native messaging through a browser extension
- Registering a protocol handler for my specific application which just transforms a URI into a curl. i.e.
app://<data> => curl -X POST -d "<data>" --unixsocket ...
Are there other ways of doing this that I'm overlooking? Any ideas would be appreciated.
google-chrome http unix firefox ipc asked Nov 22 at 14:14
Greg Linklater
116
add a comment |
up vote
0
down vote
favorite
Anyone know of a browser that supports this?
I've written a service using NodeJS and express and I'd like to limit its use to the local user 0o700 and I figured the best way to do that is using a UNIX domain socket.
Only question remains: how do I communicate with it from a browser window? Most browsers don't seem to support something along the lines of a http+unix://... scheme.
The communication needn't be two-way but that would be nice and I've considered the following:
- Native messaging through a browser extension
- Registering a protocol handler for my specific application which just transforms a URI into a curl. i.e.
app://<data> => curl -X POST -d "<data>" --unixsocket ...
Are there other ways of doing this that I'm overlooking? Any ideas would be appreciated.
google-chrome http unix firefox ipc asked Nov 22 at 14:14
Greg Linklater
116
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Anyone know of a browser that supports this?
I've written a service using NodeJS and express and I'd like to limit its use to the local user 0o700 and I figured the best way to do that is using a UNIX domain socket.
Only question remains: how do I communicate with it from a browser window? Most browsers don't seem to support something along the lines of a http+unix://... scheme.
The communication needn't be two-way but that would be nice and I've considered the following:
- Native messaging through a browser extension
- Registering a protocol handler for my specific application which just transforms a URI into a curl. i.e.
app://<data> => curl -X POST -d "<data>" --unixsocket ...
Are there other ways of doing this that I'm overlooking? Any ideas would be appreciated.
google-chrome http unix firefox ipc asked Nov 22 at 14:14
Greg Linklater
116
Anyone know of a browser that supports this?
I've written a service using NodeJS and express and I'd like to limit its use to the local user 0o700 and I figured the best way to do that is using a UNIX domain socket.
Only question remains: how do I communicate with it from a browser window? Most browsers don't seem to support something along the lines of a http+unix://... scheme.
The communication needn't be two-way but that would be nice and I've considered the following:
- Native messaging through a browser extension
- Registering a protocol handler for my specific application which just transforms a URI into a curl. i.e.
app://<data> => curl -X POST -d "<data>" --unixsocket ...
Are there other ways of doing this that I'm overlooking? Any ideas would be appreciated.
google-chrome http unix firefox ipc google-chrome http unix firefox ipc asked Nov 22 at 14:14
Greg Linklater
116
asked Nov 22 at 14:14
Greg Linklater
116
asked Nov 22 at 14:14
Greg Linklater
116
asked Nov 22 at 14:14
Greg Linklater
116
asked Nov 22 at 14:14
Greg Linklater
116
116
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432876%2fbrowse-http-over-af-unix%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
