lör 2006-12-30 klockan 12:30 +0100 skrev Torsten Kurbad: > I also had to set up an accelerator a short while ago and found it very > hard to deal with that very narrow piece of documentation. > In fact, I have a Zope server running on port 9966, and since our users > are used to that port, I set up a squid, listening on hostname:9966 and > bound Zope to localhost:9966. > I tried several combinations of vhost, vport, vport= and > corresponding cache_peer-lines, but squid insisted to catch things from > localhost:80, although that port was never mentioned in the setup. > Finally I gave up trying alternatives and switched the whole thing to > port 80, which worked... Not sure what you did, but it's damn hard to get it wrong.. http_port XXX defaultsite=your.main.site cache_peer localhost parent 9966 0 no-query originserver and if you have multiple domains then add vhost to the http_port. > >From that arose two questions: > 1) How is it possible, to accelerate "something" that is not running on > port 80? Yes. > 2) What is a "Host directive" (cf. vhost) - this term is never mentioned > again in the squid.conf.default? It's a minor typo.. should read Host header. Regards Henrik
Attachment:
signature.asc
Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel
