Re: restrict the use of some servlets

[Anonymous]

Hi !

 

 

    What about using sessions ?

 

    Why not in the login servlet put the userid (i am sure you will need it later) in the session,

Than in the second servlet check if the session exists and if the userid is in it.

If not send the login page again.

 

p.s. Session tracking uses cookies or URL rewriting.

 

 

 

Best wishes,

                    Andras.

 

-----Original Message-----
From: Cynthia Munoz <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Wednesday, June 16, 1999 9:59 PM
Subject: restrict the use of some servlets

Hi everyone in the list!!!!

      I'm again facing a problem that I don't know what it's the best to do:

some people need to update the data in the application through the web, but before do it, the user must pass the login servlet, which verifies if he's alaud to do so, then another servlet is displayed ( I mean the html response) where the user must fill all the entries. My problem is what can I do to not let anybody go to the second page without going through the first one.

 

Thanks,

Cynthia