First thanks for you quick response again :), I really appreciate it. On 2011-08-18 12:36,Jeroen Geilman wrote: > 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. You can consider this test network is a LAN inside my corporate LAN. So from this test network a connection towards my corp. intranet is analogy with some body from corp. LAN accessing internet. So I do need a forward proxy. Beside I'm simulating a real world scenario, of which they will be connected to forward proxy. >> it returns HTTP >> 403 as it requires NTLM authentication. However the apache forward proxy >> close the connection (TCP SYN) > > FIN Yap, sorry typo :(. Good catch though... >> 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) Do you think there will be principal difference from web browser client perspective whether it's connected to forward proxy or reverse proxy? I meant I don't want the client to request http::/myProxy/bla/bla (as how reverse proxy works in my understanding, please correct me if I'm wrong), but I want the client to request http://corpLAN/bla/bla via 'myProxy' (hence forward proxy), just like the real world scenario. Or in other word, what is the consequences if I configure my web browser client to use forward proxy, but then I configure the apache proxy as reverse proxy? Many thanks in advance man! Cheers //Edo
begin:vcard fn:Edoardo Tirtarahardja n:Tirtarahardja;Edoardo org:Research In Motion Corporation adr:;;3000 CentreGreen Way;Cary;NC;27513;USA email;internet:etirtarahardja@xxxxxxx title:IOT Specialist tel;work:+1(919)677-4648 tel;fax:+1(919)677-4692 tel;cell:+1(919)802-3418 url:www.rim.com version:2.1 end:vcard
--------------------------------------------------------------------- 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: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|