Description David Jencks 2010-09-13 02:43:13 EDT

Last paragraph of section 9.3 indicates that the default servlet must, when content is missing and dispatch was an include, throw a FileNotFound exception.

This bit of patch to DefaultServlet (already patched for the content-length problem with filters) seems to fix the issue:

@@ -456,7 +458,11 @@
 
             // Handle resource
             if (resource==null || !resource.exists())
-                response.sendError(HttpServletResponse.SC_NOT_FOUND);
+                if (included) {
+                    throw new FileNotFoundException("Nothing at " + pathInContext);
+                } else {
+                    response.sendError(HttpServletResponse.SC_NOT_FOUND);
+                }