... it is a filter ... notice how it says "implements Filter". The mapping in web.xml is a dead giveaway too.
I'd love to know how it detects session timeouts though. Far as I can tell it will tell people who have yet to have a session created that they've timed out. ... first trip around the block they shouldn't see that message. The only way I can think of detecting timeout, as I mentioned in an earlier post sometime back, is to put a marker of some kind out (a session cookie) when a person logs in. You could then tell, by absence of a session and presence of the marker, that the session timed out. ... I'd love to see a simpler approach (not that what I suggest is complex). I don't personally believe you can do it with fewer things than I've mentioned here. ... and please *don't* post code! It's very poor etiquette. If someone solicits something from you, send it to them and them alone - not the list (unless explicitly asked to do so, and then limit what you post to only relevant pieces of files). On Thu, 20 Jan 2005 20:43:32 -0800, Dakota Jack <[EMAIL PROTECTED]> wrote: > I was interested, again, in a filter. > > Jack > > On Thu, 20 Jan 2005 14:41:32 -0500, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > > Dakota Jack wrote: > > I was looking for a filter that detected sessions that had expired and > > rerouted the request to a login or other appropriate page. > > > > -------------------------------------------- > > > > That's what this does, specifically the following section of code: > > > > Dakota Jack <[EMAIL PROTECTED]> > > 01/20/2005 11:07 AM > > > > I was looking for a filter that detected sessions that had expired and > > rerouted the request to a login or other appropriate page. > > > > Jack > > -- Eddie Bush --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
