Redirect Inbound HTTPS/HTTP Requests Based on URL

[Tenet]

Hi there,

I've been diggiing around for a while with this one. Basically I would like to know if it is possible to configure pfSense to redirect inbound https traffic based on the URL. e.g.

You have a small network with an Exchange server for OWA/OMA/RPC over HTTP and a seperate Terminal Services Gateway server behind pfSence with a single WAN and single IP.

As both the servers require 443 traffic, could the inbound requests for https://mail.server.com and https://tsgateway.server.com be directed to the appropriate server??

Thanks.

[hoba]

This could only be done when using multiple IPs at your WAN and resolving each host name to a different IP. Other option is to setup an https page that redirects traffic depending on the hostname that was accessed to https://mail.server.com:444 or https://tsgateway.server.com:445. In that case allhpstnames would resolve to the same IP but the different services (OWA and Terminalserver) would live on different ports.

[Tenet]

Thanks for the reply.

So, are you saying to set the HTTPS page up on the pfSense box? Or forwarding all HTTPS traffic to an IIS box inside the network and letting that do the re-direction?

I would prefer not to have to stick another box in, and really don't want to terminate the connections on an existing box (the point of the ts gateway is to pre-authenticate users before they hit any of the main boxes in the network).

Would some sort of reverse-proxy do the trick?

[hoba]

That's the only solution that came to my mind or let's say the easiest one.