Route from prefix dns name

[stanthewizard]

Hello

I'd like to know if it is possible to port route inside the lan from the prefixe dns name.

Ex:

toto.mydnsname.com -> machine1:80
titi.mydnsname.com -> machine2:80
tutu.mydnsname.com -> machine3:34567

Thanks for the help

[jimp]

You can do that but it requires an add-on package to proxy http based on the hostname, such as Varnish.
I believe haproxy can do it also as well as the apache+mod_security package.

Either way, it isn't possible in the base system alone because pf doesn't look that deep in the packets, it just looks at the source/destination and makes decisions that way.

[stanthewizard]

ok
I'll look into that

[stanthewizard]

Apparently … Varnish canno't be used to cache Exchange (SSL OK I understand)

[joako]

If you control the certificates there' s no issue to proxy the SSL. Or just run everything in IIS! /exchange is one site /toto is another site etc.

However look at this, I'm pretty sure Exchange needs HTTP 1.1. When I use HTTP (not HTTPS) and Squid proxy the requests fail due to HTTP 1.0 being used.

[Gloom]

Exchange 2003 or 2010? Two different beasts and need a slightly different approach. Also is it only the OWA you are trying to access or are you trying to run the outlook client in RPC over HTTP mode.

[joako]

@Gloom:

Exchange 2003 or 2010? Two different beasts and need a slightly different approach. Also is it only the OWA you are trying to access or are you trying to run the outlook client in RPC over HTTP mode.

Just to use the EWS API with our own software. Solution: place exchange IP in squid proxy "bypass proxy for this IP"  box. For some reason "Bypass all private IP"  option has no effect.