in reply to Re^4: Multiplexing HTTPS server, peer cert authentication problem.
in thread Multiplexing HTTPS server, peer cert authentication problem.

I am suggesting repairing the SSL data by sending it across from a parent process. The open "|blah" suggestion is a last resort option to prevent the need for Threads, not because there are any problems with IPC.

-M

Free your mind

  • Comment on Re^5: Multiplexing HTTPS server, peer cert authentication problem.

Replies are listed 'Best First'.
Re^6: Multiplexing HTTPS server, peer cert authentication problem.
by erroneousBollock (Curate) on Mar 06, 2007 at 14:10 UTC
    I still don't understand ;) I'm not very smart.

    In the OP, there is no use of threads. It's a single-threaded multiplexing server... works/fails the same on Windows with threads or Linux without.

    I guess I'm not effectively describing my problem; that the peer certificate authentication is screwing up.

    I don't know if the solution is to somehow go back to a more reliable 'blocking' server, or to somehow fix the multiplexing server from the OP.

    -David.
[reply]
      I am also confused as to what is implemented where, what works and where and what doesn't work and where in regard to your two solutions. Until now I had been assuming that both solutions were always losing requests, just that your multithreaded solution lost other requests after doing authentication on one or more and still not listening for a while and that the new single-threaded solution got less far because it lost the authentication request right there.

      -M

      Free your mind

[reply]
        Ah, Ok. I can clean that up ;)

        In my existing server (not posted):
        • it is single-threaded
        • the SSL peer cert authentication works
        • the server loses some requests because only accept() is non-blocking.
        In the code I posted in the OP:
        • it is single-threaded
        • it is almost entirely non-blocking
        • the server DOES NOT lose requests if peer auth is turned OFF
        • if peer auth is ON, the server gives Net::SSLeay errors and destroys the listening socket
        -David.
[reply]

In Section Seekers of Perl Wisdom