Forwarding HTTP/HTTPS traffic based on URL

httphttpsiis-7url-routing

I look for a solution to forward http/https traffic to a backend webserver based on the request url. Our current setup:

Webserver1 (Sharepoint)
Webserver2 (Reporting Services)

Both run Windows Server 2008 and IIS7. The Webserver1 receives all traffic on port 80 and 443 and hosts a website called www.example.com

Now I want the Webserver2 to be accessible as www.example.com/Reports. Unfortunately we do not have any advanced edge firewall that could route traffic based on the request url. So I wonder if there is a way to configure Webserver1 to forward all traffic if it matches www.example.com/Reports. Any way IIS7 could do this?

Suggestions are welcome..

Best Answer

IIS7 has a URL rewrite module, which, along with the Application Request Routing module, based on the URL, can be used to do what you want.

You build it all up in the UI, and it then automatically build the XML and puts it in the web.config for you.

See "Reverse proxy" (number 7) on this list.

Correct way in new versions of nginx

Turn out my first answer to this question was correct at certain time, but it turned into another pitfall - to stay up to date please check Taxing rewrite pitfalls

I have been corrected by many SE users, so the credit goes to them, but more importantly, here is the correct code:

server {
       listen         80;
       server_name    my.domain.com;
       return         301 https://$server_name$request_uri;
}

server {
       listen         443 ssl;
       server_name    my.domain.com;
       # add Strict-Transport-Security to prevent man in the middle attacks
       add_header Strict-Transport-Security "max-age=31536000" always; 

       [....]
}

Best Answer

Related Solutions

nginx HTTPS – How to Serve HTTPS with Same Config as HTTP

NGINX Redirect – How to Rewrite All HTTP Requests to HTTPS While Maintaining Sub-Domain

Correct way in new versions of nginx

Related Topic