Amos Jeffries schrieb:
We are running such a reverse proxy setup for several clients, but with Exchange 2003. 2007 and 2010 make increasing use of the webservices and autodiscover features. I am not sure in which way these influence the way proxying needs to be handled; at least the autodiscover feature influences the way you must handle your DNS and certificates setup. My suggestion: First try to do a setup with port forwarding without squid (probably better not to do this with a real Exchange server in a production network, though... ). Once you have that running you are sure you got all the certificates and DNS issues solved. Then introduce squid into the working connection (but do not forget to eliminate the port forwarding rule first!).Andrea Gallazzi wrote:Hi All, I am a newbie about squid.I am interested about squid as reverse proxy for Outlook Web App and Activesync for Exchange 2010Did Someone have experience about this?
Sure. For different reasons it might be advisable to run two separate suids on one machine, though. Fore example, it is easier to track down errors and you can monitor the services separately. On the other hand you need to change the default configuration in several places for the second squid (ports, IPs, logging places, PId file et cetera.) In any case for such setups is is wise to use test environments - it is easy to screw up your internet access and then you have a hard time from users.Is it possible to use at the same time squid as proxy and reverse proxy ?
HTH, Jakob Curdes
