Filtering Incoming HTTP Traffic (Host Header)

[hlubovac]

I'm a potential customer - I'm trying to figure out whether it's possible to direct incoming HTTP traffic to more than one server on internal network just based on the host header. For example, if I have 2 internal web servers behind WinGate proxy, can I have it forward all HTTP requests for mydomain1.com to IP address A and all HTTP requests for mycomain2.com to IP address B?

I'm currently using Windows 2000 Server as a router, and I have one web server machine publically accessible via that router. There is a need to add another machine, but 2000 server-router can forward HTTP/HTTPS traffic to only one machine on internal network. I happen to have only one public IP address.

Is WinGate proxy a solution for me? Thanks.

[adrien]

hi

WinGate does not currently do reverse proxy (looking at Host: tag to see which internal web server to forward the request to). We are adding this function to the next major release.

Regards

Adrien

[hlubovac]

I also did not know about SSL what I learned yesterday: SSL handshake happens before data is sent, so server has no idea what the host name is - which is why multiple certificates per single IP-port pair are not possible, and which is why looking into request header in order to forward the HTTPS request to corresponding internal server is not going to be possible.

I logically seems to be possible in the case of unencrypted HTTP traffic.

Thanks.