Re: [cobalt-users] SSL not working on port 81

[Olaf Alders <olaf@xxxxxxxxxxxxxxx>]

on 2/4/02 5:08 PM, flash22@xxxxxxx at flash22@xxxxxxx wrote:

> On Mon, 4 Feb 2002, Olaf Alders wrote:
> 
>> on 2/4/02 4:09 PM, David Lucas at david@xxxxxxxxxxxxxxxx wrote:
>>> Have you closed port 443 recently?
>> I'm not aware that I have.  If it were closed I'm assuming that
>> https://www.urwebhost.com would give the same error or am I missing
>> something?
> 
> you can't do https://domain:81 when you want SSL , The server can't tell
> the difference between plain http and secure except by the port number,
> you overrode the port number explicitly, so you are trying to make a
> secure connection to a plain http port ;P
> 

Okay, that *does* makes sense to me, but the rewrites in httpd.conf seem to
allow for a secure connection to the GUI:  (here's an excerpt)

if ( ssl_cert_check("/home/sites/home/certs/") =~ /^2/ ) {
    $proto = 'https';
} else {
    $proto = 'http';
}

<snip>

$rewrite_rules =
'RewriteEngine On
RewriteCond %{HTTP_HOST}                ^([^:]+)
RewriteCond %{DOCUMENT_ROOT}            !-d
RewriteRule .*     
proto://servername:81/.cobalt/error/forbidden.html [L,R]
RewriteCond %{HTTP_HOST}                ^([^:]+)
RewriteRule ^/admin/?$
RewriteCond %{HTTP_HOST}                ^([^:]+)
RewriteRule ^/siteadmin/?$
proto://servername:81/cgi-bin/.cobalt/turbo_ui/dispatch/redirect?hostname=%1
[L,R]           

<snip>

Doesn't the above allow for an https connection to the Cobalt GUI?  What I
*think* it says is "Check for digital certificate.  If it's good, connect
via https".  Have I misunderstood this?

Olaf

-- 
Olaf Alders

olaf@xxxxxxxxxxxxxxx
http://vilerichard.com

Vera and Vi's Vile Valentine:  Tue, Feb 12, Holy Joe's, Toronto

Free web stats and counters:  http://www.wundercounter.com