Arg, what a hack ;-) (and my definition is that we get into the servlet container; if it's an internal servlet, it seems good enough, and the page being served was served by a Servlet API 2.4 component)
Come on, this is a stupid feature nobody but marketting cares about (and I'd say the said marketting folks should forget about it: Netcraft can count Java powered websites well enough already). I suppose the reasoning is that IIS/6.0 adds similar self agrandizing headers that it is .NET 1.1 powered, so we have to do the same. Lame.
So the implementation of the feature has IMO to be as invisible as possible given its lack of usefulness.
OK, I was just trying to make sure we didn't miss anything. :)
Like I said (and which you confirmed), the DefaultServlet is a servlet, so adding the response header (even) to static resources may not be too far-fetched.
Jan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
