|
Home > Archive > Squid > April 2004 > [squid-users] Squid Accelerator
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
[squid-users] Squid Accelerator
|
|
| Sampei 2004-04-29, 6:54 pm |
| I Found a solution about "no route to host" messagge which appers when
browser goes to Windows Update site using only Squid Accelerator and no
proxy mode.
analyzing system.
I type in the url of my browser directly Windows Update site and not IP
addresses.
I insert into the "hosts" file, located in system directory, all server
names which W.U. wants to meet. So I
specified in this file more Ip address (correspondent to the virtual ip
address in squid accelerator) to point to the several servers necessary for
Windows Update process.
I sniffed packets and I saw an interesting thing.
Browser's client sends a "https" request to the Squid Accelerator but
Accelerator listen only to 80 port and
not 443 (https). I saw Squid acting as Proxy server listen to a particular
port but it's able to accept
https requests which are indicated inside url; so it can answer browser.
Instead Accelerator doesn't know how handling https requests because there
is the only 80 port listened.
It's possible to have the same Squid Accelerator listen on more ports or to
be able to accepr https requests ?
regards
Riccardo
| |
| Henrik Nordstrom 2004-04-29, 6:54 pm |
| On Sun, 25 Apr 2004, Sampei wrote:
> It's possible to have the same Squid Accelerator listen on more ports or to
> be able to accepr https requests ?
Yes.
https "acceleration" is most easily done with Squid-3. Also possible with
squid-2.5 + SSL update patch but then a little messy due to the lack of a
reasonable accelerator framework..
Regards
Henrik
|
|
|
|
|