Dear Henrik, Many thx for your advise, what I would need to do is to setup SSL authentication to protect user name / password when obtaining access from intranet. After logging into squid thru https, browser client from internet may change back to http (without 's') for continuing the web surfing. (Some of the intranet application like video streaming with mjepg does not working with https)
Thx & Best Regards, Jonathan Chiu OLAPL OOCL Logistics (Hong Kong) Ltd. Unit 1, 4/F, Sun Hung Kai Centre 30 Harbour Road, Wanchai Hong Kong email: [EMAIL PROTECTED] Tel: 852. 2990-0174 Fax: 852. 2824-9017 -----Original Message----- From: Henrik Nordstrom [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 24, 2004 5:29 PM To: JONATHAN CHIU (ISD-OLAPL/HKG) Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [squid-users] reverse ssl problem. On Wed, 24 Mar 2004 [EMAIL PROTECTED] wrote: > Henrik, > > Referring to point 2, do you mean squid 3 supports https over some > virtual directories while some other virtual directories still using > http? Yes. > Is it applicable to authentication (with / without https) over certain > virtual directories? Yes, this too. Btw, what do you refer to by virtual directories? Squid-3 in reverse proxy mode can accept http/https requests (with SSL termination), then do any decision on where this should be forwarded and forwarded requests can use https/http per your decisions on how it should be forwarded. With the help of redirectors you can also rewrite the URL-path while the URL is forwarded, but as long as you do not need to rewrute the URL-path (what is after the host name) redirectors is not needed. Regards Henrik IMPORTANT NOTICE Email from OOCL is confidential and may be legally privileged. If it is not intended for you, please delete it immediately unread. The internet cannot guarantee that this communication is free of viruses, interception or interference and anyone who communicates with us by email is taken to accept the risks in so doing. Without limitation, OOCL and its affiliates accept no liability whatsoever and howsoever arising in connection with the use of this email. Under no circumstances shall this email constitute a binding agreement to carry or for provision of carriage services by OOCL, which is subject to the availability of carrier's equipment and vessels and the terms and conditions of OOCL's standard bill of lading which is also available at http://www.oocl.com.
