On 2011-08-18 18:09, Edoardo Tirtarahardja wrote:
On 2011-08-18 11:26,Jeroen Geilman wrote:
On 2011-08-18 17:08, Edoardo Tirtarahardja wrote:
Hi,
I read from mod_proxy description in Apache 2.2 that the default worker
does not use the HTTP Keep-Alive.
Is there a way how to enable it for forward proxy configuration?
You mean, from apache working as a forward proxy to the remote origin
server?
Can you imagine how bad that would be ?
Well, this is a very isolated forward proxy within a very small test
network. The reason is when I'm hitting our intranet site,
You should be using Proxypass, as you apparently need a reverse proxy.
it returns HTTP
403 as it requires NTLM authentication. However the apache forward proxy
close the connection (TCP SYN)
FIN
when delivering this HTTP 403 response to
the client, causing the client to immediately display the HTTP 403.
From a computer that directly connected to our corp. LAN, I can see that
if the TCP connection is kept alive, then the browser will re-send the
request with NTLM authentication negotiation and then it works.
I"m new in apache server, but I have done quite some google search and it
seems apache does not have module to be NTLM proxy, i.e. perform NTLM
auth. on the client behalf. The module for NTLM if I understand it
correctly, is only to be used in reverse proxy or to authenticate the
windows client.
So pass on the authentication to the proxy...
ProxyPass supports this (and does it by default AFAIK)
--
J.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [email protected]
" from the digest: [email protected]
For additional commands, e-mail: [email protected]
