RE: [squid-users] swap.log size continuing to grow?

From: Thomas Nilsen <Thomas.Nilsen@dont-contact.us>
Date: Fri, 1 Sep 2006 08:59:59 +0200

Suggest you configure this in stages.

1. Get Interscan to work on port 8080 and pass it's request on the the
parent proxy in the other company. Configure your browser to use your
interscan server IP and port 8080 as proxy and test.

2. Once step 1 works. Configure squid to use parent proxy on
localhost:8080 and make sure it works. I think there are some
restrictions with running squid on port 80 (like you have to run as root
to bind to it), so you might want to choose a different port - like
3128. But that's up to you.

Thomas

-----Original Message-----
From: wangzicai [mailto:wangzicai@cn.panasonic.com]
Sent: Friday, September 01, 2006 8:49 AM
To: Thomas Nilsen
Cc: squid-users@squid-cache.org
Subject: RE: [squid-users] swap.log size continuing to grow?

Thanks
I have changed the squid prot to 80 , but the server can not connect to
the internet directly it must throw another proxy(server in another
company).
In the intrascan I set the proxy to that proxy and the port is also 8080
When I try to access the internet the error occers:
InterScan Error
InterScan HTTP Version 3.81-Build_1084 $Date: 04/06/2005 18:36:0048$
Can't connect to the original server: (any proxy server`s name):8080

-----Original Message-----
From: Thomas Nilsen [mailto:Thomas.Nilsen@roxar.com]
Sent: Friday, September 01, 2006 2:32 PM
To: wangzicai
Cc: squid-users@squid-cache.org
Subject: RE: [squid-users] swap.log size continuing to grow?

You need to change the squid port as well (http_port) of course, so both
don't listen to 8080 - unless interscan and squid bind to different
interfaces. Apart from that it should be fine.

Thomas
-----Original Message-----
From: wangzicai [mailto:wangzicai@cn.panasonic.com]
Sent: Friday, September 01, 2006 8:22 AM
To: Thomas Nilsen
Cc: squid-users@squid-cache.org
Subject: RE: [squid-users] swap.log size continuing to grow?

Thanks
If :
In the I changed the Interscan`s working port to 8080,and change the
squid`s configuration the line: <<cache_peer 127.0.0.1 parent 8080 3130
no-query>> It will be work?
Regards
garlic
-----Original Message-----
From: Thomas Nilsen [mailto:Thomas.Nilsen@roxar.com]
Sent: Friday, September 01, 2006 1:56 PM
To: squid-users@squid-cache.org
Subject: RE: [squid-users] swap.log size continuing to grow?

You can't with that setup. If you want the users details logged in
squid, you need to swap it around so that squid uses Interscan as its
parent. As long as Interscan is passing the request on to Squid, squid
is always going to log the server IP.

Regards,
Thomas

-----Original Message-----
From: wangzicai [mailto:wangzicai@cn.panasonic.com]

Sent: Friday, September 01, 2006 2:54 AM
To: squid-users@squid-cache.org
Subject: RE: [squid-users] swap.log size continuing to grow?

Hello everyone
I have a proxy server machine.I am using squid-2.5.stable14 with
InterScan VirusWall for Unix in a same computer.the port of InterScan
VirusWall for Unix is 80 and the port of squid is 8080.

______________ ______________ _____________
| user |----------->| InterScan |-----------> | squid |
|_____________| |_____________| |_____________|

In the user`s internet I input the server`s ip and 80.
Now ,in the access.log I can not get the user`s access record. The ip is
the server1s ip. Like this
127.0.0.1 - - [24/Aug/2006:12:53:53 +0800] "GET http://www.google.co.jp/
HTTP/1.0" 200 4328 TCP_MISS\:FIRST_UP_PARENT .....
How can I solve it.

Regards
garlic

DISCLAIMER:
This message contains information that may be privileged or confidential
and is the property of the Roxar Group. It is intended only for the
person to whom it is addressed. If you are not the intended recipient,
you are not authorised to read, print, retain, copy, disseminate,
distribute, or use this message or any part thereof. If you receive this
message in error, please notify the sender immediately and delete all
copies of this message.
Received on Fri Sep 01 2006 - 01:00:16 MDT

This archive was generated by hypermail pre-2.1.9 : Sun Oct 01 2006 - 12:00:03 MDT