Re: a second http listener in one server

One thought is to have my SSL client factory class return a ServerSocket
(from createServerSocket) that can return either a normal Socket or
an SSL Socket from its accept method.  This would allow me to use a
single configuration for both services.  The ssl socket could
be specified as 'org.w3c.jigsaw.sslport' in 'http-server.props'.

--Kevin

> 
> 
> I am attempting to create a second listener in the jigsaw server.
> I have done the following:
> 
> 1) cd <Jigsaw Root>/Jigsaw/config
> 2) cp http-server.props http2-server.props
> 
> 3) changed the following properties in http2-server.props:
> 
> org.w3c.jigsaw.propfile
> org.w3c.jigsaw.port
> 
> 4) run jigsaw
> 
> This seems to work fine for static files (I can access files on
> the new port).  However, servlets no longer seem to be configured
> correctly (they are served out as flat files).  I'm not sure if
> this is the correct way to do what I want, but I couldn't find
> anything in the docs.
> 
> My reason for wanting a second server:
> 
> I have extended the class 'org.w3c.jigsaw.http.socket.SocketClientFactory'
> to add SSL support.  When I modify the config property
> 'org.w3c.jigsaw.http.ClientFactory' in 'http-server.props' to
> point to my new class (and add a few additional properties such
> as the location of a Java KeyStore), my SSL class seems to work
> fine.
> 
> However, I would also like to listen on a different port for non-SSL
> connections.  My goals are to (1) run only one jigsaw server and
> (2) to be able to use the same configuration (except for the port #
> and ClientFactory) for the two services.
> 
> Any help would be greatly appreciated.
> 
> 
> Thanks,
> Kevin Regan
> kevin@differential.com
> 
> 
>

Received on Tuesday, 4 May 1999 03:38:24 UTC