Hi, Clem In the Apache link that I provided, it stated that below Apache v2.0.58 supports RPC over HTTP. Any version of Apache above that version does not support RPC. Two reasons: 1. it is not a standard. 2. patents by Microsoft if Apache uses it. Ruiyuan Jiang -----Original Message----- From: Clem [mailto:clemfree@xxxxxxx] Sent: Friday, May 25, 2012 2:19 AM To: Ruiyuan Jiang Cc: squid-users@xxxxxxxxxxxxxxx Subject: Re: Need help to configure MS Exchange RPC over HTTP Hi Ruiyuan, >Client -> Apache (hop1) -> IIS 7 -> exchange 2007 It works the setup and just I could not have the latest Apache. Otherwise I will continue to use Apache reverse proxy. The latest Apache does not support MS RPC over http which is posted on the internet. What do you mean when you say that the latest Apache does not support MS RPC OVER HTTP, whereas your version supports it ?? That's not make sense ? If I can do Client -> Apache reverse proxy -> IIS RPC -> exchange 2007, I'll install it as soon as possible ! Thx Clem Le 24/05/2012 21:52, Ruiyuan Jiang a écrit : > By the way, NTLM works with windows 7 client through Apache here. > > > Hi, Clem > > I am reading your post > > http://www.squid-cache.org/mail-archive/squid-users/201203/0454.html > > In the post, someone stated that NTLM auth does not support: > > It's facing the double hop issue, ntlm credentials can be sent only on one hop, and is lost with 2 hops like : client -> squid (hop1) IIS6 rpx proxy (hop2) -> exchange 2007 > > That is not true. Here we have the setup: > > Client -> Apache (hop1) -> IIS 7 -> exchange 2007 > > It works the setup and just I could not have the latest Apache. Otherwise I will continue to use Apache reverse proxy. The latest Apache does not support MS RPC over http which is posted on the internet. > > https://issues.apache.org/bugzilla/show_bug.cgi?id=40029 > > I am not sure why squid does not support NTLM auth to the backend exchange server. > > Ruiyuan > > > > > > This message (including any attachments) is intended > solely for the specific individual(s) or entity(ies) named > above, and may contain legally privileged and > confidential information. If you are not the intended > recipient, please notify the sender immediately by > replying to this message and then delete it. > Any disclosure, copying, or distribution of this message, > or the taking of any action based on it, by other than the > intended recipient, is strictly prohibited. > > This message (including any attachments) is intended solely for the specific individual(s) or entity(ies) named above, and may contain legally privileged and confidential information. If you are not the intended recipient, please notify the sender immediately by replying to this message and then delete it. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, by other than the intended recipient, is strictly prohibited.
