Re: [squid-users] Reverse Proxy + Exchange OWA issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks Amos - I will try the configuration change first and look into the new version. On 11-11-04 8:44 PM, Amos Jeffries wrote: On 5/11/2011 5:03 a.m., Rick Chisholm wrote: I'm not intimidated by that option, but I prefer to use ports (which is still compiling from source FWIW) to make update management easier. Also this is a mission critical production box and I can't just blindly throw new versions at it without finding out what the issue is and why a certain solution (3.2) is the answer. I would guess the problem is OWA being broken in its use of HTTP/1.1. In particular the Expect: 100-continue feature to enable better persistent connections. You can try toggling the ignore_expect_100 configuration option (OFF is probably needed). 2.7 (and 3.1) only have partial support for that feature. With that ignore directive to cause a quick reject or a client timeout to happen (5 minutes a coincidence? ). 3.2 is needed to make chunking and continue work through Squid (avoiding the timeouts). * in particular 3.2.0.8 is the most stable and production usable of the 3.2 series. Amos - -- Rick Chisholm sysadmin Parallel42 e. rchish...@parallel42.ca m. 519-325-8630 w. www.parallel42.ca -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk613kgACgkQeE4GKUWrEKtjsgCeK7R0//5Pm96/zjlZdl1qhQXv Lf8AoI2E8Ev0cZhCiuAYjTy6uX/4tcfx =6HtK -END PGP SIGNATURE-
[squid-users] Reverse Proxy + Exchange OWA issue
I've read about this problem, just wondering if there were any fixes. We have a squid reverse proxy in from of OWA Exchange 2010. When a client connects through the proxy to the full/enriched OWA version there is about a 5 minute pause before everything starts working. After than, everything works great. If you sign-out and back in, you are still fine, unless you clear your cache, then you get the pause again. The light versions of OWA work fine. Squid version is 2.7.9_1 -- Rick Chisholm Systems Administrator Parallel42
Re: [squid-users] Reverse Proxy + Exchange OWA issue
On 04/11/2011 16:55, Rick Chisholm wrote: clear your cache, then you get the pause again. The light versions of OWA did you tried the 3.2 branch? as let say 3.2.0.8? Eliezer
Re: [squid-users] Reverse Proxy + Exchange OWA issue
3.2 does not appear to be available in the BSD ports tree at this time. On Fri, November 4, 2011 11:39 am, Eliezer Croitoru wrote: On 04/11/2011 16:55, Rick Chisholm wrote: clear your cache, then you get the pause again. The light versions of OWA did you tried the 3.2 branch? as let say 3.2.0.8? Eliezer -- Rick Chisholm Systems Administrator Parallel42
Re: [squid-users] Reverse Proxy + Exchange OWA issue
On 04/11/2011 17:41, Rick Chisholm wrote: 3.2 does not appear to be available in the BSD ports tree at this time. compile it yourself.. it pretty simple.. Eliezer On Fri, November 4, 2011 11:39 am, Eliezer Croitoru wrote: On 04/11/2011 16:55, Rick Chisholm wrote: clear your cache, then you get the pause again. The light versions of OWA did you tried the 3.2 branch? as let say 3.2.0.8? Eliezer
Re: [squid-users] Reverse Proxy + Exchange OWA issue
I'm not intimidated by that option, but I prefer to use ports (which is still compiling from source FWIW) to make update management easier. Also this is a mission critical production box and I can't just blindly throw new versions at it without finding out what the issue is and why a certain solution (3.2) is the answer. On Fri, November 4, 2011 11:45 am, Eliezer Croitoru wrote: On 04/11/2011 17:41, Rick Chisholm wrote: 3.2 does not appear to be available in the BSD ports tree at this time. compile it yourself.. it pretty simple.. Eliezer On Fri, November 4, 2011 11:39 am, Eliezer Croitoru wrote: On 04/11/2011 16:55, Rick Chisholm wrote: clear your cache, then you get the pause again. The light versions of OWA did you tried the 3.2 branch? as let say 3.2.0.8? Eliezer -- Rick Chisholm Systems Administrator Parallel42
Re: [squid-users] Reverse Proxy + Exchange OWA issue
On 5/11/2011 5:03 a.m., Rick Chisholm wrote: I'm not intimidated by that option, but I prefer to use ports (which is still compiling from source FWIW) to make update management easier. Also this is a mission critical production box and I can't just blindly throw new versions at it without finding out what the issue is and why a certain solution (3.2) is the answer. I would guess the problem is OWA being broken in its use of HTTP/1.1. In particular the Expect: 100-continue feature to enable better persistent connections. You can try toggling the ignore_expect_100 configuration option (OFF is probably needed). 2.7 (and 3.1) only have partial support for that feature. With that ignore directive to cause a quick reject or a client timeout to happen (5 minutes a coincidence? ). 3.2 is needed to make chunking and continue work through Squid (avoiding the timeouts). * in particular 3.2.0.8 is the most stable and production usable of the 3.2 series. Amos
