Hi Achim, Thanks. I can't get it working. We are currently using PAX 1.1.2, so perhaps it just simply isn't merging the connector information in that version.
If I disable the connectors in the OSGi configuration and just use the jetty.xml configuration, the confidential auto redirect does not work either. <?xml version='1.0' encoding='UTF-8'?> <Configure class="org.eclipse.jetty.server.Server"> <Call name="addConnector"> <Arg> <New class="org.eclipse.jetty.server.nio.SelectChannelConnector"> <Set name="host"><Property name="jetty.host" /></Set> <Set name="port"><Property name="jetty.port" default="8090"/></Set> <Set name="maxIdleTime">300000</Set> <Set name="Acceptors">2</Set> <Set name="statsOn">false</Set> <Set name="confidentialPort">8453</Set> <Set name="name">jettyConn1</Set> <Set name="lowResourcesConnections">20000</Set> <Set name="lowResourcesMaxIdleTime">5000</Set> </New> </Arg> </Call> <Call name="addConnector"> <Arg> <New class="org.eclipse.jetty.server.ssl.SslSelectChannelConnector"> <Set name="Port">8453</Set> <Set name="maxIdleTime">30000</Set> <Set name="keystore">C:/SAA/Reims/RCS70/custom/reims/configuration/tomcat.keystore</Set> <Set name="password">OBF:1yf21sox1x821xfd1xfp1x8s1sot1yf4</Set> <Set name="keyPassword">OBF:1yf21sox1x821xfd1xfp1x8s1sot1yf4</Set> </New> </Arg> </Call> </Configure> I guess we will need to upgrade. Regards Ed From: Achim Nierbeck <bcanh...@googlemail.com> To: General OPS4J <general@lists.ops4j.org> Date: 08/10/2012 16:20 Subject: Re: *Confidential: Re: How can I set the ConfidentialPort on the HTTP Connector in the PAX Web Jetty Server ? Hi Ed, it should be possible to do an edit of an existing connector, you need to referenz it by name, though pax-web will also try to merge both configuration of the std. HTTP Connector and one provided by a jetty.xml (at least in 2.x). Regarding your question, yes with the name it's possible to add multiple connectors, which is the purpose of the connector in the sample. In that sample it's used to bind certain applications to certain connectors, for more details see [1] Regards, Achim [1] - http://team.ops4j.org/browse/PAXWEB-396 2012/10/8 Ed Roberts <ed.robe...@saaconsultants.com>: > Hi Achim, > > I will open a ticket. Many thanks for your assistance. > > Just to clarify, what is it exactly that stops the jetty.xml configuration > from attempting to *add* another connector > and instead *edit* an existing one ? Is it the name ? (i.e. <Set > name="name">jettyConn1</Set> from your link example) > > Regards > Ed > > > > > From: Achim Nierbeck <bcanh...@googlemail.com> > To: General OPS4J <general@lists.ops4j.org> > Date: 08/10/2012 15:20 > Subject: Re: *Confidential: Re: How can I set the ConfidentialPort on > the HTTP Connector in the PAX Web Jetty Server ? > > > > Hi Ed, > > in that case since you need another HTTP - Connector you need to add a > special jetty.xml. > An example for adding or enhancing a http connector can be found at [1]. > Though, thinking more about this it should/could be a useful > enhancement if this behavior would be added per default if a SSL Port > is configured. > Would you mind opening a new Issue for this, so we don't loose track of it. > > regards, Achim > > [1] - > https://github.com/ops4j/org.ops4j.pax.web/blob/master/samples/jetty-config-fragment/src/main/resources/jetty.xml > > > 2012/10/8 Ed Roberts <ed.robe...@saaconsultants.com>: >> Hi Achim, >> >> Thanks for the quick response. >> >> The Confidential Port is a redirect-port setting on the HTTP Connector >> which the web server should automatically redirect the client to if the > Web >> Application is configured to demand a secure connection; i.e. > CONFIDENTIAL >> in the security constraint section of the web app's web.xml. >> >> It is the same value as the SSL Connector port configuration, but it has > to >> be defined on the HTTP Connector. >> >> Thanks >> >> Ed >> >> >> >> From: Achim Nierbeck <bcanh...@googlemail.com> >> To: General OPS4J <general@lists.ops4j.org> >> Date: 08/10/2012 14:54 >> Subject: Re: How can I set the ConfidentialPort on the HTTP > Connector in >> the PAX Web Jetty Server ? >> >> >> >> Hi Ed >> >> I'm not quite sure I can follow, do you mean by confidential Port the >> SSL Port for webapplications? >> If so take a look at [1]. This gives you a description of how to >> configure Secure ports. >> >> Regards, Achim >> >> [1] - http://team.ops4j.org/wiki/display/paxweb/SSL+Configuration >> >> 2012/10/8 Ed Roberts <ed.robe...@saaconsultants.com>: >>> >>> Hi >>> >>> I am deploying the PAX Web Jetty Bundle (and other bundles) to get PAX >> Web. >>> I can set the majority of properties through the OSGi Configuration. >>> I just need one more, the Confidential Port on the HTTP Connector in >> order >>> to *hopefully* trigger automatic redirection for CONFIDENTIAL web >>> deployments. >>> >>> The only way I can see of doing this is via the jetty.xml configuration >>> file, which can be referenced in the OSGi configuration. >>> However, try as I might, I cannot see a simple way of just setting the >>> Confidential Port. >>> >>> I have seen examples online setting the HTTP port, and so set the file > up >>> as follows >>> >>> <?xml version='1.0' encoding='UTF-8'?> >>> <Configure id="Server" class="org.eclipse.jetty.server.Server"> >>> <Set name="confidentialPort">8453</Set> >>> </Configure> >>> >>> Of course that class does not even have a setter that matches, so I can >> see >>> why that fails. >>> >>> There just aren't any examples of someone using the Get element to drill >>> down to the connectors. >>> >>> Can anyone shed any light, please. Does the lack of examples mean that I >>> must bypass the entire HTTP Connector configuration from the OSGi >>> configuration ? >>> >>> Thanks for any help >>> >>> Ed >>> >>> >>> _______________________________________________ >>> general mailing list >>> general@lists.ops4j.org >>> http://lists.ops4j.org/mailman/listinfo/general >> >> >> >> -- >> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC >> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> >> Committer & Project Lead >> OPS4J Pax for Vaadin >> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project >> Lead >> blog <http://notizblog.nierbeck.de/> >> >> _______________________________________________ >> general mailing list >> general@lists.ops4j.org >> http://lists.ops4j.org/mailman/listinfo/general >> >> >> >> _______________________________________________ >> general mailing list >> general@lists.ops4j.org >> http://lists.ops4j.org/mailman/listinfo/general > > > > -- > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> > Committer & Project Lead > OPS4J Pax for Vaadin > <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project > Lead > blog <http://notizblog.nierbeck.de/> > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/> _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general