Burton M. Strauss III wrote: >So from ntop's view it's getting an unencrypted request on the https: port??? >Or is it being double encrypted (once by the https: request and once by >stunnel)??? > >I'm totally confused... > >Wait a minute: > >"It's *not* stunnel that sets up a SSL connection with the server (i.e. to >ntop's SSL), the client >sets up a SSL connection to stunnel (i.e. https: in the browser), which sets up >a "normal" (i.e. http:) connection to ntop." > >OK, now I get it - the path is this: > >(browser) https: -> https: stunnel http: -> http: ntop > > Now you got it. ;-)
>Which makes sense, because this IS a normal connection (from ntop's >perspective). > > Precisely! In ntop's perspective it's a normal http connection. I wanted to make a normal http: connection to ntop but a SSL connection from my browser. So if images are displayed in this setup, which they do, then SSL is not to blame, and nor is the browser. The fault *must* be ntop's SSL code. >I suspect that some browsers are opening multiple https: connections and that's >causing some kind of deadlock. I'll have to read the code paths in ntop to see >if it's obvious... > > k, that could be the problem for the "hanging", but not for the not displaying of the images, right? >-----Burton > -- Mike. _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
