Ondra Kudlik wrote:[...]
Googling gave me this which worked ;)
HeadRequire "Host: .*mrtablecloth-vi.com.*"
That's a snip of a long pound.cfg file that details out every URL
specifically. I had a catch-all at the bottom like this:
where port 81 would be my yet-to-be configured squid cache proxy.
Interestingly, I noticed this in /var/log/messages after the client
tried unsuccessfully to hit the site:
Aug 14 18:34:21 server167 pound: backend 220.127.116.11:81 connect:
which seems to indicate that Pound did *not* transfer the request to
port 8080 (a Zope instance). However, I can hit the site with no
problems, and the client reports a "Welcome to Web.vi \n Zope" where
web.vi is my personal site and name of the server (localhost.web.vi) and
also resolves for me. So I'm confused as to where the problem is...in
Pound, or in Zope...and what it is.
I also noticed this in my log:
Aug 14 18:34:21 server167 pound: no back-end "GET
/1280/s/c/x/en-us/index.pt HTTP/1.1" from 18.104.22.168
Aug 14 18:34:22 server167 pound: no back-end "GET /favicon.ico HTTP/1.1"
which is a comcast IP address, telling me nothing ;) But the "no
back-end" argument is interesting. This was after the client tried to
hit the site after before my discovering the port 81 issue. It is
statistically probable that no other requests came to the box in the
interval. After I changed the port to 8080, there were no complaints in
the log, even after the client tried to hit the site again. Ideas as to
how to proceed?