I think the conclusion was that the basic strategy to control where users can and can't enter your application's page navigation involves checking properly for required parameters at the beginning of each action.
If the required parameters are missing, you have a design choice, whether to direct the user to an error page, or somewhere else, for instance the start of the appropriate series of pages. You have to be able to distinguish the reason why the required parameters are not there, in order to determine if it is a technical error or a misguided user.
It also depends on what you have in your querystrings.
HTH Adam
On 09/09/2003 08:11 PM veera maria wrote:
Hello,
What is the best way to prevent user to request web application's actions from browser manually?
E.g. user is using web application and taking it's current url to clipboard. Then user goes e.g. to Google for surfing for a while. After surfing (s)he pastes web applications url back to browser's address field. Best technique in Struts applicaton to prevent this?
Vera
_________________________________________________________________ Tilaa nyt Hotmail postit kännykkääsi! http://www.msn.fi/mobiili/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- struts 1.1 + tomcat 4.1.27 + java 1.4.2 Linux 2.4.20 RH9
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
