Hi,
Can someone take a look at it the following issue which I ran into?
Here is the details:
Outline: squid 2.6 as the reverse-proxy for IIS (SharePoint) site.
IIS uses the NTLM authentication.
Regarding the squid document, squid 2.6+ or squid 3.1+ support
NTLM passthru authentication by Connect
ective_user squid
b. access.log
1327980594.156 72 16.212.0.105 TCP_MISS/503 4098 GET
http://usplsvulx104.elabs.eds.com/ - FIRST_UP_PARENT/main text/html
Except the relevant configurations, I am not sure I miss any other factors.
Thanks,
Kimi
On 31/01/2012, Henrik Nordström wrote:
> mån 2012-01
Hi,
Could anyone give any suggestion to configure squid as a reverse-proxy
to work with IIS/SharePoint plus NTLM?
If it doesn't work, any other suggestion to setup the similar
environment. I mean to improve the web access performance with
reverse-proxy ( cache server )?
Thanks,
Kimi
Thanks Amos,
Currently, we use a VM ( vmware) to host a RHEL with squid running.
I change the back-end site with only an IIS test web site which is
hosted on the same IIS system.
And it's just a png image file. And it seem working.
On RHEL side, there is no limitations on outgoing on iptables rul
GET
http://ids-ams.elabs.eds.com/ is ALLOWED, because it matched 'all'
2012/01/11 13:22:09.386| TCP connection to
wtestsm1.asiapacific.hpqcorp.net/80 dead
2012/01/11 13:22:09.387| ConnStateData::swanSong: FD 9
My squid environment information:
RHEL6.0 64bit.
squid v 3.1.4
Thanks,
~Kimi
O
t squid be running, I do test like this
http://ids-ams.elabs.eds.com
The 404 error page is shown.
That's why I am wondering squid could be as reverse-proxy with IIS
SharePoint as back-end?
Thanks,
~Kimi
On 11/01/2012, Amos Jeffries wrote:
> On 11/01/2012 6:28 p.m., kimi ge(巍俊葛) wrote
Hi,
I have an issue to make squid 3.1.x to work with IIS SharePoint as the
back-end.
The details are listed below.
1. squid 3.1.x is running as a reverse-proxy.
2. The back-end is IIS SharePoint Site with domain authentication required.
That means only the valid domain user could access this S
