status code 207

2001-05-16 Thread Murthy Gorty
Hi, I need to send a status code of 207 as part of my WebDav-servlet response. But, Tomcat gives me a MissingResourceException because this status code is not defined in org.apache.core.LocalStrings.properties. How do I work around that? What is the standard way of adding custom status codes? Is

Session-expiry bug v2.0

2001-02-14 Thread Murthy Gorty
Hi, I posted a question last week about this and I'm including the conclusions of that posting anticipating more responses.. :-) I'm using tomcat 3.2.1 final release. Tomcat's check for Session Expiry happens in a background thread (StandardManager::processExpires()) that calls Session.getLas

Re: Session-expiry bug? getLastAccessedTime

2001-02-12 Thread Murthy Gorty
Hi, I debugged thru Tomcat3.2.1 source code this morning and it too has the same problem: Session.access() is called only once per request, before the request is processed (called by findSession in StandardManager) This would mean that getLastAccessedTime() always gives the time of (last-1) req

Re: Session-expiry bug? getLastAccessedTime

2001-02-11 Thread Murthy Gorty
--- > From: Craig R. McClanahan <[EMAIL PROTECTED]> > To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > Subject: Re: Session-expiry bug? getLastAccessedTime > Date: Sat, 10 Feb 2001 12:52:24 -0800> >

Session-expiry bug? getLastAccessedTime

2001-02-09 Thread Murthy Gorty
Hi, I noticed a problem with session timeouts in Tomcat3.2.1 The background thread that recycles sessions based on timeouts uses Session.getLastAccessedTime(). The session object itself has two variables lastAccessedTime and thisAccessedTime. - public