From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: [Development] proxy: Entering HTTPS ports into the WebUI
Date: Thu, 15 Mar 2012 19:06:15 +0100 [thread overview]
Message-ID: <8b52ec7836993423c3433878a3555f39@mail01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
Hello,
I wanted to read your opinion on the following topic:
When entering another HTTPS port to the list of allowed HTTPS ports
on the proxy page, you still cannot access the internet through it.
It is needed to enter the port to the list of HTTP ports as well.
Is this behaviour intended? Do we want to change it by automatically
adding all HTTPS ports to the HTTP list? Or do I just understand that
setting wrong.
Michael
reply other threads:[~2012-03-15 18:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8b52ec7836993423c3433878a3555f39@mail01.ipfire.org \
--to=michael.tremer@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