HTTP proxy in OpenBSD 5.8 (replacing Apache ProxyPass)
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I'm trying to replace Apache with OpenBSDs httpd but can't figure out what to do with my ProxyPass statements.
In apaches conf it looks like this
ProxyPass /someurl http://192.168.123.123/someotherurl
ProxyPassReverse /someurl http://192.168.123.123/someotherurl
- I thought I should use relayd for this, but how do I do the URL rewrite?
- Would I set up relayd to listen on port 80 and forward some things to different internal machines and the rest to httpd on localhost?
openbsd reverse-proxy openbsd-httpd
add a comment |
I'm trying to replace Apache with OpenBSDs httpd but can't figure out what to do with my ProxyPass statements.
In apaches conf it looks like this
ProxyPass /someurl http://192.168.123.123/someotherurl
ProxyPassReverse /someurl http://192.168.123.123/someotherurl
- I thought I should use relayd for this, but how do I do the URL rewrite?
- Would I set up relayd to listen on port 80 and forward some things to different internal machines and the rest to httpd on localhost?
openbsd reverse-proxy openbsd-httpd
add a comment |
I'm trying to replace Apache with OpenBSDs httpd but can't figure out what to do with my ProxyPass statements.
In apaches conf it looks like this
ProxyPass /someurl http://192.168.123.123/someotherurl
ProxyPassReverse /someurl http://192.168.123.123/someotherurl
- I thought I should use relayd for this, but how do I do the URL rewrite?
- Would I set up relayd to listen on port 80 and forward some things to different internal machines and the rest to httpd on localhost?
openbsd reverse-proxy openbsd-httpd
I'm trying to replace Apache with OpenBSDs httpd but can't figure out what to do with my ProxyPass statements.
In apaches conf it looks like this
ProxyPass /someurl http://192.168.123.123/someotherurl
ProxyPassReverse /someurl http://192.168.123.123/someotherurl
- I thought I should use relayd for this, but how do I do the URL rewrite?
- Would I set up relayd to listen on port 80 and forward some things to different internal machines and the rest to httpd on localhost?
openbsd reverse-proxy openbsd-httpd
openbsd reverse-proxy openbsd-httpd
asked Jan 27 '16 at 19:24
EVKEVK
211
211
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Great question! OpenBSD's newly written httpd
is not a fully-featured web-server, and nor is it intended to be. As for relayd
, which was the precursor to httpd
, I do not believe that it has any ability to do what you require, either.
The best general-purpose replacement for Apache bar none is still nginx.
It is readily available in the OpenBSD ports tree as www/nginx
, and can be easily installed as a precompiled package with pkg_add(1)
— doas pkg_add nginx
.
Once you install nginx, you would use the proxy_pass
directive, and it'll probably look like this:
location /someurl
proxy_pass http://192.168.123.123/someotherurl;
As for ProxyPassReverse
, nginx has a more appropriate name for it — proxy_redirect
, and the default value of default
should already be sufficient for your needs (that is, if your ProxyPassReverse
and ProxyPass
directives both had the same value). Good luck!
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
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%2funix.stackexchange.com%2fquestions%2f258090%2fhttp-proxy-in-openbsd-5-8-replacing-apache-proxypass%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Great question! OpenBSD's newly written httpd
is not a fully-featured web-server, and nor is it intended to be. As for relayd
, which was the precursor to httpd
, I do not believe that it has any ability to do what you require, either.
The best general-purpose replacement for Apache bar none is still nginx.
It is readily available in the OpenBSD ports tree as www/nginx
, and can be easily installed as a precompiled package with pkg_add(1)
— doas pkg_add nginx
.
Once you install nginx, you would use the proxy_pass
directive, and it'll probably look like this:
location /someurl
proxy_pass http://192.168.123.123/someotherurl;
As for ProxyPassReverse
, nginx has a more appropriate name for it — proxy_redirect
, and the default value of default
should already be sufficient for your needs (that is, if your ProxyPassReverse
and ProxyPass
directives both had the same value). Good luck!
add a comment |
Great question! OpenBSD's newly written httpd
is not a fully-featured web-server, and nor is it intended to be. As for relayd
, which was the precursor to httpd
, I do not believe that it has any ability to do what you require, either.
The best general-purpose replacement for Apache bar none is still nginx.
It is readily available in the OpenBSD ports tree as www/nginx
, and can be easily installed as a precompiled package with pkg_add(1)
— doas pkg_add nginx
.
Once you install nginx, you would use the proxy_pass
directive, and it'll probably look like this:
location /someurl
proxy_pass http://192.168.123.123/someotherurl;
As for ProxyPassReverse
, nginx has a more appropriate name for it — proxy_redirect
, and the default value of default
should already be sufficient for your needs (that is, if your ProxyPassReverse
and ProxyPass
directives both had the same value). Good luck!
add a comment |
Great question! OpenBSD's newly written httpd
is not a fully-featured web-server, and nor is it intended to be. As for relayd
, which was the precursor to httpd
, I do not believe that it has any ability to do what you require, either.
The best general-purpose replacement for Apache bar none is still nginx.
It is readily available in the OpenBSD ports tree as www/nginx
, and can be easily installed as a precompiled package with pkg_add(1)
— doas pkg_add nginx
.
Once you install nginx, you would use the proxy_pass
directive, and it'll probably look like this:
location /someurl
proxy_pass http://192.168.123.123/someotherurl;
As for ProxyPassReverse
, nginx has a more appropriate name for it — proxy_redirect
, and the default value of default
should already be sufficient for your needs (that is, if your ProxyPassReverse
and ProxyPass
directives both had the same value). Good luck!
Great question! OpenBSD's newly written httpd
is not a fully-featured web-server, and nor is it intended to be. As for relayd
, which was the precursor to httpd
, I do not believe that it has any ability to do what you require, either.
The best general-purpose replacement for Apache bar none is still nginx.
It is readily available in the OpenBSD ports tree as www/nginx
, and can be easily installed as a precompiled package with pkg_add(1)
— doas pkg_add nginx
.
Once you install nginx, you would use the proxy_pass
directive, and it'll probably look like this:
location /someurl
proxy_pass http://192.168.123.123/someotherurl;
As for ProxyPassReverse
, nginx has a more appropriate name for it — proxy_redirect
, and the default value of default
should already be sufficient for your needs (that is, if your ProxyPassReverse
and ProxyPass
directives both had the same value). Good luck!
answered Jul 4 '16 at 3:45
cnstcnst
1,50021338
1,50021338
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f258090%2fhttp-proxy-in-openbsd-5-8-replacing-apache-proxypass%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