Is the following a bug or a part of the Servlet 2.2 spec?
http://machine:port/appname/WEB-INF/inside.jsp would get served but
http://machine:port/appname/WEB-INF/inside.html would not?
--
Richard F. Wan
email: [EMAIL PROTECTED]
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
> > http://machine:port/appname/WEB-INF/inside.jsp would get served but
> > http://machine:port/appname/WEB-INF/inside.html would not?
> Neither one should be served back to a direct client request for these
> URLs. The server is prohibited from ret
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
> It's legal to access either of these URLs, however, in the following ways:
> RequestDispatcher rd =
> getServletContext().getRequestDispatcher("/WEB-INF/inside.jsp");
> rd.forward(request, response);
Is the ability to request dispatch
Petr Jiricka <[EMAIL PROTECTED]> wrote:
> I noticed that the time to serve the first servlet or a JSP has increased
> dramatically. I traced this down to the initialization of
> java.security.SecureRandom, which is used for generating the session IDs.
On
is there a way to configure the server.xm