You are viewing limited content. For full access, please sign in.

Question

Question

Setting up a Reverse Proxy to only forward traffic from Forms, not Weblink

asked on February 2, 2017

I'm hoping someone can help out on the exact step by step details needed to do as stated in the title of this thread. From what I see on Answers, for most people its an all or nothing. 

Our client has 3 servers (LFS-Internal, LFWEB-Internal, and DMZ-External). 

Their External server hosts their Weblink (Public Portal). 

The Forms Portal runs on the internal LFWEB server because they wanted to use their AD accounts externally and this was the only way (that we knew of) to do so. 

What we want to do is forward any traffic that hits https://laserfiche.customer.com/Forms to their internal LFWEB server. If someone hits https://laserfiche.customer.com/Weblink  it will not forward and the DMZ IIS will load the Weblink page. 

We had this all working but since then the DMZ server crashed and their was no backup, and the documentation has been misplaced. 

I know we had a reverse proxy with a condition I believe. I forget if the reverse proxy is at the server level in IIS, default website in IIS, or did we have to have an empty 'forms' site in IIS and have the reverse proxy there?

 

Help would greatly be appreciated as their Forms are currently down to the public. 

 

Thank you

0 0

Replies

replied on February 2, 2017

I don't have much personal experience setting it up, but the IIS feature you are looking for is called Application Request Routing.  You should be able to configure it to only forward requests for certain URLs.

0 0
replied on February 3, 2017

Thanks Brian, I forgot to mention I have already installed and configured ARR, but there is more to it than that. From what I understand of it; ARR 'enabled' allows the reverse proxy to work. The thing I need still is the correctly configured reverse proxy. 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.