FWIW, I tried using camel-jetty at first and configured the parameter sendServerVersion, but couldn't get it to work.
Then I tried the plain CXF JAX-RS. Can't work as well. Still looking into it. Regards, Allan C. On Mon, Jul 18, 2016 at 9:07 AM, Allan C. <allan...@gmail.com> wrote: > Hi Claus, > > It's plain CXF JAX-RS. > > I will look into it and get back to you soon. > > Regards, > Allan C. > > On Sat, Jul 16, 2016 at 4:04 PM, Claus Ibsen <claus.ib...@gmail.com> > wrote: > >> You say using CXF JAXRS. Is that camel-cxf or plain JAX-RS with CXF >> then you may need to look at those to turn off that option, or in >> karaf in general. >> >> >> >> >> >> On Wed, Jul 13, 2016 at 5:48 AM, Allan C. <allan...@gmail.com> wrote: >> > Hi Claus, >> > >> > I did a bit of tweaking here and there and unfortunately can't get it to >> > work. However, although I'd completely taken out jetty stuffs in my >> > blueprint, when I do a post to my CXF JAXRS server, the header "Server" >> > still is returned, with the value "Jetty(9.2.15.v20160210)". >> > >> > When I list the jetty features running, I can see pax-jetty has the same >> > version. >> > karaf@root()> feature:list | grep jetty >> > jetty | 9.2.10.v20150310 | | Started | >> > standard-4.0.5 | >> > jetty | 8.1.14.v20131031 | | Uninstalled | >> > standard-4.0.5 | >> > cxf-http-jetty | 3.1.5 | | Started | cxf-3.1.5 >> > | >> > pax-jetty | 9.2.15.v20160210 | | Started | >> > org.ops4j.pax.web-4.2.6 | >> > pax-jetty-spdy | 4.2.6 | | Uninstalled | >> > org.ops4j.pax.web-4.2.6 | >> > pax-http-jetty | 4.2.6 | | Started | >> > org.ops4j.pax.web-4.2.6 | >> > camel-jetty | 2.16.3 | | Uninstalled | >> camel-2.16.3 >> > | >> > camel-jetty9 | 2.16.3 | | Started | >> camel-2.16.3 >> > | >> > >> > Thus, I am guessing that CXF is running on top of pax-jetty. I will >> look at >> > if there's anything in CXF or pax-jetty that will let me configure the >> > parameter "sendServerVersion" or something similar. >> > >> > NB: >> > Jetty9 component configuration in XML DSL is not available in the >> official >> > camel-jetty page. Just in case anyone needs a quick setup, this is the >> > configuration. Most, if not all, of the values are from the Karaf 4.0.5 >> > default jetty.xml file. >> > >> > <bean id="jetty9" >> > class="org.apache.camel.component.jetty9.JettyHttpComponent9"> >> > <property name="socketConnectors"> >> > <map> >> > <entry key="8080"> >> > <bean class="org.eclipse.jetty.server.ServerConnector"> >> > <argument> >> > <bean class="org.eclipse.jetty.server.Server"> >> > <argument> >> > <bean class="java.net.InetSocketAddress"> >> > <argument value="0.0.0.0" /> >> > <argument value="8080" /> >> > </bean> >> > </argument> >> > </bean> >> > </argument> >> > <argument> >> > <list> >> > <bean class="org.eclipse.jetty.server.HttpConnectionFactory"> >> > <argument> >> > <bean class="org.eclipse.jetty.server.HttpConfiguration"> >> > <property name="secureScheme" value="https" /> >> > <property name="securePort" value="8443" /> >> > <property name="outputBufferSize" value="32768" /> >> > <property name="requestHeaderSize" value="8192" /> >> > <property name="responseHeaderSize" value="8192" /> >> > <property name="sendServerVersion" value="true" /> >> > <property name="sendDateHeader" value="false" /> >> > <property name="headerCacheSize" value="512" /> >> > </bean> >> > </argument> >> > </bean> >> > </list> >> > </argument> >> > <property name="port" value="8080" /> >> > <property name="idleTimeout" value="30000" /> >> > <property name="name" value="jettyServerConnector" /> >> > </bean> >> > </entry> >> > </map> >> > </property> >> > </bean> >> > >> > Regards, >> > Allan C. >> > >> > On Tue, Jul 12, 2016 at 6:35 PM, Allan C. <allan...@gmail.com> wrote: >> > >> >> Hi Claus, >> >> >> >> Thanks for your reply. >> >> >> >> Yes, I basically switched from using Fuse 6.2.1 (Karaf 2.4.0 I think) >> to >> >> Karaf 4.0.5, thus providing the opportunity to upgrade some of the >> other >> >> features such as camel, jetty and hibernate. >> >> >> >> I will try it out and let you know soon. >> >> >> >> Regards, >> >> Allan C. >> >> >> >> On Tue, Jul 12, 2016 at 6:12 PM, Claus Ibsen <claus.ib...@gmail.com> >> >> wrote: >> >> >> >>> Hi >> >>> >> >>> You can also configure the sendServerVersion on the component level, >> >>> you can try that >> >>> >> >>> If using blueprint its something like this >> >>> >> >>> <bean id="jetty" class="...JettyComponent"> >> >>> <property name="sendServerVersion" value="false"/> >> >>> </bean> >> >>> >> >>> >> >>> On Tue, Jul 12, 2016 at 11:11 AM, Claus Ibsen <claus.ib...@gmail.com> >> >>> wrote: >> >>> > Hi >> >>> > >> >>> > Is the only thing you have upgraded is Camel? Or did you also >> upgrade >> >>> Karaf ? >> >>> > >> >>> > On Mon, Jul 11, 2016 at 4:31 AM, Allan C. <allan...@gmail.com> >> wrote: >> >>> >> Hi, >> >>> >> >> >>> >> I have recently upgraded camel from 2.15.1 to 2.16.3, and from >> using >> >>> >> camel-jetty8 to camel-jetty9. In my jetty route I have >> >>> >> sendServerVersion=false. >> >>> >> >> >>> >> Before upgrade, the server doesn't return the header Server. After >> >>> upgrade, >> >>> >> it now returns the header Server along with Jetty version, which is >> >>> >> 9.2.15.v20160210. >> >>> >> >> >>> >> My camel context is running on Karaf 4.0.5, which uses pax-jetty. >> Are >> >>> there >> >>> >> additional configurations I am missing? >> >>> >> >> >>> >> Regards, >> >>> >> Allan C. >> >>> > >> >>> > >> >>> > >> >>> > -- >> >>> > Claus Ibsen >> >>> > ----------------- >> >>> > http://davsclaus.com @davsclaus >> >>> > Camel in Action 2: https://www.manning.com/ibsen2 >> >>> >> >>> >> >>> >> >>> -- >> >>> Claus Ibsen >> >>> ----------------- >> >>> http://davsclaus.com @davsclaus >> >>> Camel in Action 2: https://www.manning.com/ibsen2 >> >>> >> >> >> >> >> >> >> >> -- >> Claus Ibsen >> ----------------- >> http://davsclaus.com @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 >> > >
