| [jetty-users] Not sure how to set this up. |
|
Ok, I'm a little confused regarding how all of the xml files and
start.ini interact in Jetty 9.x. Here's what I'd like to do ** have an HTTP 1.1 server instance listening on port 80 ** have an SNI-enabled server instance listening on port 443 ** have separate deployment directories for each instance, into which I will put XML files like this one: <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <Configure class="org.eclipse.jetty.webapp.WebAppContext"> <Set name="contextPath">/</Set> <Set name="war">/var/www/SomeWebsite</Set> <Set name="virtualHosts"> <Array type="String"> <Item>SomeWebsite.com</Item> <Item>www.SomeWebsite.com</Item> </Array> </Set> </Configure> and I have something similar working on my production server, but it's running an earlier version of Jetty (9.0.something or 9.1.something) and things look like they've changed significantly (or maybe I'm just tired - it's almost 2am here). I think my #1 problem is that I'm playing around with 9.3 locally and I can't figure out how to get Jetty to read jetty-ssl-extended-context.xml. It wants to load {jetty.base}/etc/keystore even though I modified jetty-ssl-extended-context.xml to look for the keystore somewhere else. Help, please? Thanks --
Lobos Studios - Website and Mobile App Design & Development; IT Support; Computer Maintenance Toll Free 877.919.4WEB - Apple Valley 760.684.8859 - Los Angeles 310.945.2410 - Cleveland 216.242.4010 www.LobosStudios.com * www.facebook.com/LobosStudios * @LobosStudios |