[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[cobalt-users] Secure admin cert & slow connections



Folks;

   Got an odd problem, seemingly related to the one Mr. Lasman saw last fall,
although not identical since he was receiving hard errors and I'm not.

   I was screwing around today and created a self-signed certificate for SSL
(I am not going to be using it for ecommerce, but rather to protect some
specific transactions I want to make with the machine), and as a side effect
the admin routines (which I use only when absolutely required, thanks) are
now served by the secure server. (Kinda ugly, that - would make more sense if
the script actually asked permission to pull a stupid stunt like that, but
let it go for now.)

   And it is _glacially_ slow.

   I don't mean it's a little lagged, I mean it took almost five minutes to
load the "main" admin webpage, and I only have . It works fine, and other
pages are somewhat speedier, but loading the main page takes forever to load.
I'm using Netscape 4.5/Mac, but the slowdown doesn't _seem_ to be on the
client side; I keep getting a lot of, "Host ...:81 contacted. Waiting for
reply..." notes that seem to hang there forever. Once it finally _does_ load,
it works just peachie; I haven't received any errors from the thing, and can
do what needs to be done.

   Tests pulling regular site pages through https doesn't anecdotally show
any difference in time between http and https...the problem seems
_specifically_ limited to the administration perl script.

   Has anyone seen anything like this? There was no resolution posted to Mr.
Lasman's thread that I could find in the archives, so I don't know what hios
eventual outcome was, but I'd be curious to know if there's anyone else who
needs to start loading the admin pages, then go for lunch while they load...

         Charlie

   P.S. Oh, while I'm on the subject, if/when I _delete_ the self-signed
certificate I'm playing with, will the admin go back to being served by the
insecure, or will it simply get confused and not accept _any_ connections? I
know what it _should_ do, but then it _should_ ask permission before forcing
the secure server to port 81, too...

         Me