On Tue, 25 Jan 2011 17:54:23 +0000, smudly Quickhands wrote: > I was planning on using SQUID as the front end for my Exchange 2010 > server. I have already setup the Exchange server and have installed a SSL > certificate mail.myco.com on it. > > I was going to try and split the certificate and use if for the SQUID > server as well. I just realized thatthe only external domain I have for > accessing Exchange 2010 is mail.myco.com and I was planning on using it for > OWA and Outlook Anywhere and possibly activesync later. > > Will this be a problem? Can SQUID handle these connections as well? If the connections go via HTTP they can go through Squid. If they don't you may need to configure the box underneath Squid to route the packets on to their actual destination. NP: Squid-3.1 has some problems with NTLM and Windows 7 Outlook requiring HTTP/1.1, but that is easily resolved by using a 3.2 build. > > Has anyone else set it up this way? This is the first mention of Exchange 2010 to come through the list. So hopefully someone else out there has a better idea from hands-on with the specific version. Past history with Exchange has shown a variety of strange effects each time they upgraded the use of HTTP and SSL features. Things should turn out okay once the new hacks are figured out, but I hope you are not pressed for time to complete this. Amos
