The "preferred" way of doing this is to use connection pooling. The
primary reasons are scalability, speed and simplicity. If you have 5,000
people using your app at the same time, by your method you will have to
have 5,000 connections to the database (one per user) stored in the
various sessio
Why do you need to forward the request from index.html to index.jsp?
Can't you simply set index.jsp to be a directory index page (e.g.,
DirectoryIndex index.html index.jsp)?
Abhinav Gautam wrote:
Hi,
I am having serious problems with Tomcat. It just happened that without
any reason the web ser
I think what you're looking for is an application "framework". There are
a number of them at Apache:
Struts: http://jakarta.apache.org/struts/index.html
Turbine: http://jakarta.apache.org/turbine/index.html
Tapestry: http://jakarta.apache.org/tapestry/index.html
Cocoon: http://cocoon.apache.org/
WEB-INF has a special meaning to a servlet container (e.g., Tomcat) and
must be a top-level directory in your web application directory (in this
case, it must be located at .../ROOT/WEB-INF).
Download the servlet specification and take a look at section 9.5:
http://java.sun.com/products/servlet
This error means that you directly referenced the login page. This is an
annoyance with Tomcat security realms: you get authenticated, but since you
weren't going anywhere in the realm, you get the HTTP Status 400 error.
Rather than accessing the login page, simply access any page that is
protected
See
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/archives/
for past versions of Tomcat.
Be aware, though, that Tomcat 4.0.4 and 4.0.5 have security vulnerabilities.
See
http://jakarta.apache.org/site/news.html
for 9Oct2002 and 24Sep2002 for more information.
Andrew
-Original Message--
I'm having a similar problem (also using struts) in Tomcat > 4.0.2.
Scenario: I have a search page that performs a search and brings up a
results page. On the results page, you can click on a hyperlink to get
additional information about an element of the search. If you have clicked
on a hyperlink
I'm using form-based authentication in Tomcat 4.1.12 -- it works great!
However, I have two questions about Tomcat authentication:
1) Many end-users bookmark the login page. So, the first time they login
everything works as expected, but when they use the bookmark, they get the
invalid reference
See the following thread which explains why the problem arises and how to
fix it.
http://www.mail-archive.com/tomcat-user@;jakarta.apache.org/msg67093.html
To the above solution, I made two additional changes because
1) the list of duplicated parameters on the url grew as it was paged -- e.g.
url
