From: "R. W. Rodolico" <rodo@dailydata.net>
To: documentation@lists.ipfire.org
Subject: Re: New version of Proxy access control list documentation
Date: Sat, 10 Sep 2016 01:32:46 -0500 [thread overview]
Message-ID: <57D3A90E.5060609@dailydata.net> (raw)
In-Reply-To: <CAK9whhz2+7XDfK=yAz+7WtVdHhvSGF1VtE6V3UhFvKTTz8z9MQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1533 bytes --]
I am a total novice when it comes to SQUID, but I understood that pretty
well. I think it is very good.
Rod
On 09/08/2016 07:41 AM, Carlo Fusco wrote:
> Dear List,
>
> please review the following wiki section:
>
> http://wiki.ipfire.org/en/configuration/network/proxy/wui_conf/access
>
> which I heavily modified from the previous text. The part I modified is
> in between:
> *
> *
> begin section to be reviewed
>
> end section to be reviewed
>
> I particular, please check carefully the part before the image of the
> web interface and the paragraphs titled:
>
> Disable internal proxy access to Green from other subnets
> /
> /
> and /
>
> /Disable internal proxy access to other subnets from the Blue IP space
> (except the IPFire machine itself):
>
> Let me state that the author(s) of this text did an amazing job and
> allowed me to understand how to configure the proxy the way I wanted. My
> modifications are intended only to try to make it more clear to a
> beginner and to correct an error in the text, as discussed previously in
> other mails on this list.
>
> I welcome any criticism. I will wait until you give me permission to
> remove the "under review" notice.
>
> Thank you.
> *
> *
> Cheers.
>
> --
> Carlo Fusco
>
>
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
>
--
Rod Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
http://www.dailydata.net
next parent reply other threads:[~2016-09-10 6:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAK9whhz2+7XDfK=yAz+7WtVdHhvSGF1VtE6V3UhFvKTTz8z9MQ@mail.gmail.com>
2016-09-10 6:32 ` R. W. Rodolico [this message]
[not found] <CAK9whhzPO5zSkwhZQfFoZa2Da9squcsbHDc2du=cguJLXZYPbQ@mail.gmail.com>
2016-09-14 17:09 ` Matthias Fischer
2016-09-15 2:04 ` R. W. Rodolico
2016-09-15 10:38 Carlo Fusco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57D3A90E.5060609@dailydata.net \
--to=rodo@dailydata.net \
--cc=documentation@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox