I doubt you have that degree of control wrt your container. What you might consider is a small refactoring that would cause you to also check for the session, if any, and ... whatever attribute you have there that signals a "valid, logged-in" user. CMA is seperate from your web application, and so you don't have as "fine-tuned" control over it.
Oh - or you might try doing a redirect. You say it's null on the next request, so forcing another request may be the solution... assuming you haven't painted yourself into a corner you can't redirect out of. Regards, Eddie Graham Lounder wrote: >In my logoff action, I'm invalidating my session. The problem is, the >getRemoteUser still returns the username when I forward to my jsp page. >Once I process another request, the remote user is set to null. > >Is there any way in my LogoffAction servlet to set the remote user to null >before forwarding to the jsp page? > >Graham > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
