Hi,
On 14.09.2016 12:38, Carlo Fusco wrote:
Hello,
I made a mistake. I have completely forgotten that the documentation of how to edit squid.conf existed at the following link: http://wiki.ipfire.org/en/configuration/network/proxy/extend/conf_edit
Don't worry - mistakes are human and you're doing a great job, IMHO.
Basically, I made a worst and redundant copy of that document. So I edited again http://wiki.ipfire.org/en/configuration/network/proxy/wui_conf/access to remove my text regarding this specific issue and on its place I put a link to that document. I believe this way it's still informative while remaining brief and to the point. I also modified
http://wiki.ipfire.org/en/configuration/network/proxy/extend/conf_edit
to add to it my example of ACL usage on how to prevent the connection to the IPFire machine from the blue IP space. If there are objections, please feel free to revert the edits and criticize here anything you find wrong. I welcome it. I am doing all this to help the project, however I do it also to learn, any criticism would help me succeed in this regard.
As far as I can see: looks good. ;-)
One point that came to my view while testing some squid-versions here.
Perhaps it would be necessary to add a small comment that changes to '/var/ipfire/proxy/advanced/acls/include.acl' only take place after hitting 'Save and restart' on the GUI(!?).
If you restart 'squid' through console with '/etc/init.d/squid restart' 'squid' is "only restarted", but 'include.acl'-contents won't get written to 'squid.conf'.
This once happened to me and since then I always use the GUI after making changes there. But test this first, to confirm.
Best, Matthias