From: "R. W. Rodolico" <rodo@dailydata.net>
To: documentation@lists.ipfire.org
Subject: Re: New version of Proxy access control list documentation
Date: Wed, 14 Sep 2016 21:04:22 -0500 [thread overview]
Message-ID: <57DA01A6.1000606@dailydata.net> (raw)
In-Reply-To: <CAK9whhzPO5zSkwhZQfFoZa2Da9squcsbHDc2du=cguJLXZYPbQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]
One of the big problems with the wiki is organization. When it was first
started, it had a nice organization, but that has degraded over time.
Because of that, we sometimes write articles that already exist.
Additionally, there is some old information out there that really should
not be there.
Sorry you had to run into it so soon.
On 09/14/2016 05:38 AM, 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
>
> 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.
>
> 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 prev parent reply other threads:[~2016-09-15 2:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAK9whhzPO5zSkwhZQfFoZa2Da9squcsbHDc2du=cguJLXZYPbQ@mail.gmail.com>
2016-09-14 17:09 ` Matthias Fischer
2016-09-15 2:04 ` R. W. Rodolico [this message]
2016-09-15 10:38 Carlo Fusco
[not found] <CAK9whhz2+7XDfK=yAz+7WtVdHhvSGF1VtE6V3UhFvKTTz8z9MQ@mail.gmail.com>
2016-09-10 6:32 ` R. W. Rodolico
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=57DA01A6.1000606@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