Author Topic: squid 3.2  (Read 592 times)

Offline yodelu

  • PCLinuxOS Tester
  • Sr. Member
  • *******
  • Posts: 317
squid 3.2
« on: November 14, 2012, 12:44:50 AM »
i just updated from squid 3.1.16 (which worked fine) to 3.2 - which not work as i expect
i use squid with intercept in squid.conf  (eg http_port 192.168.0.100:90 intercept)
specifying a proxy route in client browser is optional = the client CAN specify proxy the route OR NOT  - that's the way squid 3.1.16 work
now, in squid 3.2, if the parameter intercept is used, then the client's browser dosen't work if the proxy route is specified on the client side
something is wrong here !?   

thx!

Offline AndrzejL

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 12797
  • RLU #490933
    • Wordpress On The Wardrobe...
Re: squid 3.2
« Reply #1 on: December 03, 2012, 03:35:51 PM »
The latest squid from repo works just fine here however some changes in the /etc/squid/squid.conf were necessary.

Here is my /etc/squid/squid.conf for comparison

http://pastebin.com/cJw4Ldec

of coz depending on Your network setup it will vary but at lease You can check if lines exist in my config and were they # or not.

Here is my /etc/init.d/squid

http://pastebin.com/RrxijqJ4

which i modified to get rid of "file descriptors" issue

and for the transparent proxy to work I had to add as root:

Code: [Select]
REDIRECT loc 3128 tcp 80
before this line:

Code: [Select]
#LAST LINE -- ADD YOUR ENTRIES BEFORE THIS ONE -- DO NOT REMOVE
in

Code: [Select]
/etc/shorewall/rules
and then run

Code: [Select]
service shorewall restart
Sometimes You can debug squid with:

Code: [Select]
su
Code: [Select]
root's password
Code: [Select]
service squid restart
also

Code: [Select]
squid -k parse
ran as root will show You how Your config works.

http://pastebin.com/w8kWpcx6

Regards.

AndrzejL
« Last Edit: December 03, 2012, 03:51:34 PM by AndrzejL »

Offline yodelu

  • PCLinuxOS Tester
  • Sr. Member
  • *******
  • Posts: 317
Re: squid 3.2
« Reply #2 on: December 03, 2012, 11:11:21 PM »
thx AndrzejL for reply
yes i saw that squid 3.2 use a quite different conf file so i "wrote" a new one for the new squid
after all squid 3.2 work fine but in the different way as 3.1 does
in your squid.conf i see that you use two ports - one for transparent mode an one for normal mode
maybe that's the way the new squid works ...
 thx again !

Offline AndrzejL

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 12797
  • RLU #490933
    • Wordpress On The Wardrobe...
Re: squid 3.2
« Reply #3 on: December 04, 2012, 03:50:48 AM »
No problem.

I am pretty sure that the transparent mode is not necessary however if You use the transparent mode only You will get info in the logs that the intercept mode is not enabled. Both modes are preferred transparent mode is used.

Check the "directives" in my config. Some of them are # out due to a simple fact - they are no longer needed in squid 3.2.x. Some were added (to block some sites from being cached and to block certain file types from being cached).

I am sure You will get it running again.

Cheers.

AndrzejL
« Last Edit: December 04, 2012, 04:12:03 AM by AndrzejL »