On 28 Jan 2010, at 17:36, Alexander Klimetschek wrote: > On Thu, Jan 28, 2010 at 17:19, Ian Boston <i...@tfd.co.uk> wrote: >> For the sling main servlet I think this is relatively easy to achieve. > > Yes. > >> Should anything be done for other servlets that might be registered directly >> with the OSGi Http Service. > > No, because that is outside the scope of Sling. Whoever does that in > his custom app, and provides an implementation of TRACE, should handle > that himself.
ok > >> IIUC, that bypasses all the normal Jetty config which is why TRACE gets >> through in the first instance. > > Isn't Jetty calling the OSGi http service? Yes, Jetty Server.handle(.. ) goes via a number of intermediate handles and direct into the PAX web handler HttpServletHandler that dispatches to the servlet. AFAICT, there is not reference to the method at any point in the chain of handlers, so no chance of filtering Trace methods. On the basis of the above this looks like a patch for the main servlet, I will open a Jira. ian > > Regards, > Alex > > -- > Alexander Klimetschek > alexander.klimetsc...@day.com
