Re: SSL with metuxmpm (was Re: Metuxmpm test failed)

-                                                 [email protected]
---------------------------------------------------------------------

On Mon, 6 Oct 2003, Christian Skarby wrote:

> Anyway, If I have understood the concepts right, we need a way for the
> multiplexer to differensiate between ssl and non-ssl ip/ports. For ssl
> ip/ports we could probably forward the connection right away to the right
> ssl-processor, whereas we'll have to do the normal peeking in the
> http-header in order to decide which non-ssl-processor that should serve
> the request.

If you are referring to a setup where one SSL processor handles all SSL
requests regardless of their vhost domain I'd say that this is not
something MetuxMPM should handle as it can also be handled by a totally
separate Apache (listening on port 443 only).

But MetuxMPM (or the multiplexer) should be able to handle SSL connections
(all SSL connections made with one certificate with wildcards, see my
previous posting), parse the vhost/get request, and the pass the request
to the proper processor.

Regards