On 21/04/17 15:37, 钱国正 wrote:
I know squid+ecap can modify http response with a relatively fast
speed, and I have done that before.
But, in real environment, there is a lot of reqeusts, that don't need
processs http response, which would make network slow.
So I am thinking whether I can use libn
I know squid+ecap can modify http response with a relatively fast speed, and I
have done that before.
But, in real environment, there is a lot of reqeusts, that don't need processs
http response, which would make network slow.
So I am thinking whether I can use libnetfilter_queue to judge that ht
Some more info:
cache.log is able to rotate.
Only access.log not rotating
root@paproxy:/# ls -alt /var/log/squid
total 15540
drwxrwxr-x 9 root syslog 4096 Apr 20 14:42 ..
drwxr-xr-x 2 proxy proxy 4096 Apr 20 06:25 .
-rw-r- 1 proxy proxy63 Apr 20 06:25 cache.log
-rw-r- 1
Hi Eliezer
Thank you for the fast reply.
Squid is listening on 3128 on the server.See netstat output below.
We would like to fix the logrotate script (if this is being used?) rather
that wait for Ubuntu to fix the Squid package (which may take a while).
There is no cron job under root or proxy
On 20/04/17 16:44, turgut kalfaoğlu wrote:
On 04/19/2017 06:44 PM, dijxie wrote:
Do you recieve the same error while connecting to
https://www.wikipedia.org?
Yes I do.
I also tried to connect to the IP address as well; and that gives me
the same error.
The browser didn't say anything; it was
On 20/04/17 14:07, Dan Charlesworth wrote:
Thanks Amos.
As far as I can tell the only device upstream of the proxy is a
relatively basic gateway/firewall. I doubt it's capable of messing
with HTTP headers (and loading the site directly, as opposed to using
the proxy lets it load fine behind t
Hey CM,
From the output I understand that there wasn't a change in squid packaging for
16.04 and they still use rc\init.d startup scripts.
Also they probably use the same logrotate scripts from very long ago.
We first must understand if squid is running and it seems that systemd sees it
as runni
Hi Eliezer
Thank you for the response, and sorry for the late reply.
As requested, here are the output of the commands you suggested:
root@paproxy:/# systemctl status squid
● squid.service - LSB: Squid HTTP Proxy version 3.x
Loaded: loaded (/etc/init.d/squid; bad; vendor preset: enabled)
Ac
After two and a bit weeks on this I finally have the Raspberry Pi working as a
transparent proxy server utilising Diladele to provide web filtering. I'm going
to trial it all for the next few weeks to ensure that it's stable but so far
the results have been positive and its working with HTTP and
