Fwd: [squid-users] Cache_Peer Question (Newbie)

From: Gonzalo Arana <gonzalo.arana@dont-contact.us>
Date: Fri, 25 Aug 2006 15:44:03 -0300

Hi,

The request you posted is a request that should be addressed to a web
server, not to a proxy server.

Perhaps you want your squid to be an http accelerator? If this is the
case, and if you are running squid 2.6 you should have something like:

http_port 80 virtual

(check squid.conf.default, as it should have proper documentation).

You may want to have cache_peer_access configured as well.

Have a look at http://wiki.squid-cache.org/SquidFaq/ReverseProxy

HTH,

On 8/25/06, beno <zope@2012.vi> wrote:
> Hi;
> I must misunderstand something fundamental about cache_peer. Here is my
> line in squid.conf:
>
> cache_peer 202.71.106.119 parent 7080 2020 default no-query
>
> What I want to do is configure cache_peer to:
> * Receive requests from Pound (which it is...I get a Squid error page)
> * Send _all_ requests to port 7080 unless, of course, Squid has a cached
> page, which it can then serve.
>
> I have no need of ICP, so I don't know if that "2020" (which is the port
> Squid listens on) is necessary. I am perhaps mistaken in assuming that
> Squid is the "parent" in this relationship. The error page follows.
>
> TIA,
> beno
>
>
> ERROR
>
>
> The requested URL could not be retrieved
>
> ------------------------------------------------------------------------
>
> While trying to process the request:
>
> GET / HTTP/1.1
> Host: 2012.vi
> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6
> Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
> Accept-Language: en-us,en;q=0.5
> Accept-Encoding: gzip,deflate
> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> Keep-Alive: 300
> Connection: keep-alive
> Pragma: no-cache
> Cache-Control: no-cache
> X-Forwarded-For: 200.88.97.74
>
>
>
> The following error was encountered:
>
> * * Invalid Request *
>
> Some aspect of the HTTP Request is invalid. Possible problems:
>
> * Missing or unknown request method
> * Missing URL
> * Missing HTTP Identifier (HTTP/1.0)
> * Request is too large
> * Content-Length missing for POST or PUT requests
> * Illegal character in hostname; underscores are not allowed
>
>
>

--
Gonzalo A. Arana
-- 
Gonzalo A. Arana
Received on Fri Aug 25 2006 - 12:44:09 MDT

This archive was generated by hypermail pre-2.1.9 : Fri Sep 01 2006 - 12:00:02 MDT