Re: [squid-users] Forwarding from squid to junkbuster

Actually you should use cache_peer_access to control what gets sent to
junkbuster, and never_direct to control what must be sent to a parent.

# Junkbuster is running on localhost port 8000
acl HTTP proto HTTP
cache_peer 127.0.0.1 parent 8000 7 no-query
cache_peer_access 127.0.0.1 allow http
never_direct allow HTTP

but it can be done as you did also, except that in your configuration
the junkbuster proxy will receive some requests for other protocols
(i.e. gopher and SSL).

--
Henrik Nordstrom
Squid Hacker
Shanker Balan wrote:
> 
> Hello:
> 
> Thanx for the hint. :) I added the following to squid.conf and squid is
> now forwarding to junkbuster.
> 
> /etc/squid.conf
> 
> # Junkbuster is running on localhost port 8000
> cache_peer 127.0.0.1 parent 8000 7 no-query
> acl HTTP proto HTTP
> acl FTP proto FTP
> never_direct allow HTTP
> always_direct allow FTP
> 
> Anything else that needs to be tweaked or improved? What about HTTPS? Do
> i need to add something for that too?
> 
> I set protocol FTP as direct since junkbuster does not(?) do FTP and
> things seems to be working well.
> 
> HTTP seems to be getting trapped by squid and forwarded to junkbuster.
> All FTP connections are not trapped or logged at all. Exactly what i
> wanted to achieve!
> 
> Snips from logs:
> 
> squid/access_log
> 989057957.506   1535 127.0.0.1 TCP_MISS/304 170 GET
> http://i.cnn.net/cnn/virtual/2000/code/main.js -
> FIRST_UP_PARENT/127.0.0.1 -
> 
> junkbuster/junkbuster
> /usr/sbin/junkbuster: GPC       i.cnn.net/cnn/virtual/2000/code/main.js
> 
> Thanx for your time. Perhaps some one should add this to the junkbuster
> FAQ.
> 
> -- Shanu
> 
> Henrik Nordstrom wrote,
> > See cache_peer_access/always_direct/never_direct directives.
> 
> --
> 
>  -   -   -   -   -   -   -   -   -   -  - ( Shanu )  -  -
>  Shanker Balan                                                  shanu@exocore.com