You Mean this solves the problem partially ? Or What can be done either on server side or on client side.
Is there any way this can be done? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, August 03, 2006 8:16 PM To: user@struts.apache.org; [EMAIL PROTECTED] Subject: RE: Browser History by HTTP-REFERER Do you realize that browsers are not required to send a Referer header? And that many proxies strip out such a header? You will have far better success if you create a robust application that can do the correct thing even if URLs are received out of the expected order. Trying to hamstring the browser is an exercise in futility. > -----Original Message----- > From: Raghuveer [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 03, 2006 9:37 AM > To: user@struts.apache.org > Subject: Browser History by HTTP-REFERER > > > > In my Struts Web application > i need to restict the user accessing pages from Browser > History. When i access any page from Browser History i get > http-referer=null > > So, > I am checking this by below code on Server side in All my > execute method in Struts Action File . > if(request.getHeader("REFERER")==null){ > > throw new Exception("Invalid operation"); > } > > Is this Correct way of handling ? > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
