OK, but that test really doesn't test anything. If stunnel does it's thing, it's
transparent.
The flaw could be in one of TWO places...
1) ntop's implementation may not be able to handle the request as it's coming from
those two browsers - for example, it could be a deadlock (esp as it seems to be in the
second request - maybe the browser is trying to open a 2nd connection before the 1st
is completed...)
2) The browser may be sending an invalid request for https: but not http: (i.e. a
different path internal to the browser code) (Since your test is http:, it wouldn't
test this).
-----Burton
---------- Original Message ----------------------------------
From: Mike Klinkert <[EMAIL PROTECTED]>
Date: Mon, 06 May 2002 00:06:46 +0200
>This is precisely what I did. I *am* testing tunneled http:, proving
>that SSL and the browsers are not at fault here and that the bug is in
>ntop's SSL. Maybe this was already clear to you, but not to me (and nor
>to Luca, since I haven't seen any other claim on the list of what the
>problem is).
__________________________________________________
D O T E A S Y - "Join the web hosting revolution!"
http://www.doteasy.com
_______________________________________________
Ntop mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop
