The Servlet API doc for the sendRedirect method states:
If the location is relative with a leading '/' the container interprets
it as relative to the servlet container root.
I've looked thru the Servlet Spec and can not quite figure out what they mean
by servlet container root ? Is
, the (current draft of the) 2.4
Servlet-
Spec
has changed the behavior, and so in Tomcat 5.x you can define a
HttpSessionListener that will get called before the session is
invalidated.
Charlie Toohey [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
I have been looking for a way
I have been looking for a way to execute some code when a session is
terminating due to invalidation or expiration, but before the session has
actually been terminated.
I know that implementing HttpSessionBindingListener and binding my object
into the session will allow me to execute code in
I have several groups of webapps -- all webapps in the same group access the
same database. I am defining a Resource and ResourceParams in server.xml
and using JNDI to acquire a DataSource (I'm using the Jakarta Commons
database connection pool).
The question is, should I define a
Infrequently, Tomcat is creating a new session on each request from the same
cookie, when all of the requests should be in the same session.
I am logging the cookie and session ids to debug this. What I see is that a
request comes in with cookie JSESSIONID=X. Tomcat creates a new session, with
correctly.
If the Content-type is note set correctly, Tomcat can't parse the HTTP
headers (including the cookie), so it'll create a new one.
Charlie Toohey wrote:
Infrequently, Tomcat is creating a new session on each request from the
same cookie, when all of the requests should be in the same
Yes. Entirely normal.
Read the Servlet Specification. Specifically the sections on Sessions and the
Deployment Descriptor --- the web.xml you can set the default session timeout
value for your webapp. This can be modified at run-time using a servlet API
method.
On Tuesday 14 January 2003
per the Tomcat configuration documentation at
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/context.html
you MUST define a Context with a context path equal to a zero-length string.
This Context becomes the default web application for this virtual host, and
is used to process all
state that this is necessary ?
- Charlie
On Friday 10 January 2003 01:02 pm, you wrote:
On Friday 10 January 2003 03:53 pm, Charlie Toohey wrote:
per the Tomcat configuration documentation at
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/context.html
you MUST define a Context
Hi,
I was looking thru the archives and see your suggestion below. I am also
using Apache/Tomcat. I added your configuration to my server.xml file. Now I
get the following exception in the apache_log file when starting up Apache to
install the web applications:
java.lang.SecurityException:
When configuring Apache's httpd.conf (or Vhosts.conf) with multiple
name-based virtual hosts, I can not find any documentation regarding the
WebAppConnection statement. Should I have a separate WebAppConnection within
each virtual host section, or should I just have one WebAppConnection in the
I've had better luck with the mod_webapp.so binary from Tomcat 4.0.1 than the
one from Tomcat 4.0.2. I've used it successfully with Tomcat 4.0.1, 4.0.2 and
4.0.3.
available at:
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.1/bin/linux/i386/
Also, in my environment I've
it there.
- Charlie
On Tuesday 26 February 2002 12:04 pm, you wrote:
Can't you have a logger point to tomcat log file?
Ben
- Original Message -
From: Charlie Toohey [EMAIL PROTECTED]
To: Struts Users Mailing List [EMAIL PROTECTED]
Sent: Tuesday, February 26, 2002 1:18 PM
Subject: Re
First, of all, the assumption is that you have not turned off session support
using the JSP page directive, i.e. you do NOT have
%@ page session=false
The default is true, so as long as you do not have this, you are fine.
Now, session.isNew() would continually return false if the following
14 matches
Mail list logo
