Using Apache Directives to expose a system behind a firewall.
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Using Apache Directives to expose a system behind a firewall.
I have a lan connected to the internet through a router. The router exposes port 80 to one system, 192.168.1.50. I have a set of web pages on 192.168.1.90 that I want to also expose to the internet. For instance http://example.com would go to the .50 system, while http://example.com/mark and http://example.com/mark/crud would draw data from the .90 system. My attempts at generating rewrite rules almost work, except the http://example.com/mark/crud becomes http://192.168.1.90/mark/crud, which from the internet is not resolvable.
Can someone point me to the documentation that specifically mentions how to rewrite or proxy such that I can have a tree successfully exposed?
but depending on what else is going on on the remote server, it might require more. mod_rewrite can also do this but I prefer mod_proxy. As I can remember it.
but depending on what else is going on on the remote server, it might require more. mod_rewrite can also do this but I prefer mod_proxy. As I can remember it.
if you've using an exact uri stem that also exists on the remote server, even better yes. Just as you have it there. if you might get 302's back from the end point, you can use the same config for ProxyPassReverse which will rewrite HTTPS 302s etc.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.