Your application will still need to run on a Windows server with IIS, but it can be behind your firewall. Your Apache HTTPD server would go in your DMZ and would proxy connections between the clients on the internet and the internal server. (Your firewall would need to allow those connections.)
On Mon, May 7, 2018 at 1:44 PM Charles Marcus <CMarcus@media-brokers.com> wrote:
But to be clear - I asked the Support people and was told, and I quote:
"The Webvantage, Client Portal and Mobile Server applications are .Net IIS applications that require Microsoft Windows and IIS."
So... was that just a typical response from a Windows support person who doesn't really understand web servers?
The software in question is described here:
I don't mind doing the work, I'd just rather not go down a rabbit hole trying to do something that can/will never work.
On Mon May 07 2018 13:37:36 GMT-0400 (Eastern Standard Time), Yehuda Katz <email@example.com> wrote:
Certainly. I would start with the Reverse Proxy Guide: https://httpd.apache.org/docs/2.4/howto/reverse_proxy.htmlCome back here if you have any questions.
On Mon, May 7, 2018 at 1:32 PM Charles Marcus <CMarcus@media-brokers.com> wrote:
I just want to know if this is even worth my time trying to figure out.
We have an Accounting application (.ne/IIS on Windows Server 2008R2) on our LAN, but I need to provide a window to this through the internet, and I'd really, really like to not put a Windows Server on our DMZ facing the internet directly (if I have to, it will be a separate/standalone server that redirects/proxies to the Accounting server).
first and foremost - is it even possible to setup an Apache server to do this? I loathe IIS, and also don't know much about it, but I'm also pretty much a noob when it comes to web servers in general. I do have some experience a while back with Apache, which is why I'm starting here.
If it isn't, so be it, but if it is, is it very involved?