AW: Different session timeout for local and external users

Thanks for the speedy answer to my question. Is this the only possibility? Since the filter will be called for each request, maybe this will slow down my web application Thanks again -Ursprüngliche Nachricht- Von: Mikolaj Rydzewski [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 13.

AW: Different session timeout for local and external users

I have looked at the session listeners but there I cannot access the users remote adress -Ursprüngliche Nachricht- Von: Ehlers, Kolja [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 14. November 2008 09:38 An: Tomcat Users List Betreff: AW: Different session timeout for local and external

Re: AW: Different session timeout for local and external users

Ehlers, Kolja wrote: Thanks for the speedy answer to my question. Is this the only possibility? Since the filter will be called for each request, maybe this will slow down my web application Maybe. But not likely. Search the web for 'premature optimization' ;-) -- Mikolaj Rydzewski [EMAIL

Re: AW: Different session timeout for local and external users

Mikolaj Rydzewski wrote: Ehlers, Kolja wrote: Thanks for the speedy answer to my question. Is this the only possibility? Since the filter will be called for each request, maybe this will slow down my web application Maybe. But not likely. Search the web for 'premature optimization' ;-)

AW: AW: Different session timeout for local and external users

Rydzewski [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 14. November 2008 09:42 An: Tomcat Users List Betreff: Re: AW: Different session timeout for local and external users Ehlers, Kolja wrote: Thanks for the speedy answer to my question. Is this the only possibility? Since the filter will be called

Re: AW: AW: Different session timeout for local and external users

Ehlers, Kolja wrote: is it not possible to define a global filter for all web applications? For Tomcat you can use Valves. In fact, you should really ignore additional time that such simple filter will add to request processing time. First: check if it really slows down your app. If it

AW: AW: AW: Different session timeout for local and external users

yes thanks I will do that. So I cannot just add the filter to the global web.xml at conf/web.xml? -Ursprüngliche Nachricht- Von: Mikolaj Rydzewski [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 14. November 2008 12:53 An: Tomcat Users List Betreff: Re: AW: AW: Different session timeout

RE: AW: Different session timeout for local and external users

From: Ehlers, Kolja [mailto:[EMAIL PROTECTED] Subject: AW: AW: Different session timeout for local and external users is it not possible to define a global filter for all web applications? It should be, but it will apply to all webapps, including the ones packaged with Tomcat. filter

AW: AW: Different session timeout for local and external users

An: Tomcat Users List Betreff: RE: AW: Different session timeout for local and external users From: Ehlers, Kolja [mailto:[EMAIL PROTECTED] Subject: AW: AW: Different session timeout for local and external users is it not possible to define a global filter for all web applications? It should

Re: AW: AW: Different session timeout for local and external users

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kolja, Ehlers, Kolja wrote: is it not possible to define a global filter for all web applications? Yes, but I'm not sure why you'd want to do that. If each application needs it, just enable it in all applications. If I add filter

RE: AW: Different session timeout for local and external users

From: Ehlers, Kolja [mailto:[EMAIL PROTECTED] Subject: AW: AW: Different session timeout for local and external users its located at shared/lib If it's a standalone class, it should be in shared/classes, not shared/lib. Also, make sure the class does not exist in any of the individual