Index: [Article Count Order] [Thread]

Date:  Thu, 14 Sep 2006 08:06:25 +0200
From:  Dennis <dennis (at mark) mixfans.org>
Subject:  [coba-e:06915] Re: HTTP/HTTPS Logins
To:  coba-e (at mark) bluequartz.org
Message-Id:  <4508F161.6020101 (at mark) mixfans.org>
In-Reply-To:  <4508770C.1121.29D3A63@localhost>
References:  <4508770C.1121.29D3A63@localhost>
X-Mail-Count: 06915

Keith,

The remote admin port has always been 444
the only difference is that through various updates and requests the 
secure checkbox was enabled by default causing the pages to be
redirected to https:// with port 81 I believe.
So if you uncheck the secure box than you should just use port 444 as 
the admserver is running at that port.
using port 80 for the admin interface has never been possible I believe.

Correct me if wrong. If not: I've learned something from this list <G>

Dennis

Connexions Web Solutions wrote:
> Hi Blues,
>
>  I have just noticed, which I hadnt before, that even if you untick the
>  secure box on the interface it still uses port 444.
>
> This is setup in /etc/httpd/conf.d/bluequartz.conf - a request for
> http://domain.tld/login is 302'd  to http://domain.tld:444/login.php. I
> assume this is so that all is secure until you explicitly choose not to 
> use a secure connection. 
>
> Anyone think of any reason why we couldnt
> rem out this rewrite rule and try to access the login page on port 80. 
> and is it is safe to do it ?
>
> Reason for request is we can then turn off HTTPS in the firewall, so 
> its one less port for the kiddy hackers.
>
> Rgds.
>
> Keith Reynolds
>
>