From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: How to enforce re-creation of configuration files generated by CGIs?
Date: Sat, 23 Oct 2021 08:42:00 +0200 [thread overview]
Message-ID: <b2ec92f6-623e-4c7a-bb8a-3b52deb849ff@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
Hello development folks,
while I do not think the changes related to Squid and Tor in Core Update 161
require it, I just wondered myself how to enforce recreation of the corresponding
configuration files?
Both of them are generated by CGIs ({proxy,tor}.cgi), and faking a POST request
on the command line seemed to be the wrong way to me. :-)
Am I missing something? Is there a better/ideal way for doing this?
Thanks for enlightening me, and best regards,
Peter Müller (lacking coffee)
next reply other threads:[~2021-10-23 6:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 6:42 Peter Müller [this message]
2021-10-25 12:44 ` Michael Tremer
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=b2ec92f6-623e-4c7a-bb8a-3b52deb849ff@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@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