when ever u open a page an entry is made into the history list
so for successive pages our history list grows on
suppose u open 1.html an entry is added in history list for 1.html
now u move from 1.html to 2.html
in the history list an entry for 2.html is added after 1.html
so ur hisroty list would be
1.html
2.html
and the current pointer being at 2.html
so u get the back button enabled...
For Some applications we have generally wanted to disable the back button
the way to achive it using javascript is givn below
there is a method called
window.location.replace(new page);
this command just replaces the 1.html entry with 2.html and ur hisroty list
does not grow so no back button...
because in the history list there is only one entry ,the back button is
disabled
a small sample code is given below
back.html
<HTML>
<BODY>
<A href="Javascript:window.location.replace('front.html');" >Click here</A>
</BODY>
</HTML>
front.html
<html>
<body>
Do nothing
</body>
</html>
let me know if above is of any help to u ..
regards,
Rohan
-----Original Message-----
From: Endre Stølsvik [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 04, 2002 1:53 PM
To: [EMAIL PROTECTED]
Subject: Re: Problem with the back button in the HTML
On Thu, 27 Dec 2001, Milt Epstein wrote:
| On Wed, 27 Dec 2000, Mahmood Shahzad wrote:
|
| > Hi All,
| >
| > I have to present the values submitted by a user on an HTML page
| > when the user presses the back button available in HTML. Do someone
| > have any solution.
| >
| > Browser side cash is off and I m using HTTPS.
| > Thanks in advance
|
| Check the archives, this question has come up before. Basically,
| there is no way to disable client-side actions, what you need to do is
| set things up so you can detect it on the server-side and handle it
| appropriately.
Well..
Use a "poster"/"parameters" page, and a "renderer" page. This fools all
browsers. This has indeed been up on the list a couple of times.
The idea is that the poster accepts all the parameters, and then just
redirects your browser to the renderer. The browser sees this new redirect
address, sees it being the same address as it rendered "the last time",
and doesn't store a new history entry. If you follow this through, using
only one poster and one renderer page for your whole webapp, then you can
click around your web application for hours, and then, when you click back
one single time, you'll end up on NYtimes or whereever you came from in
the first place.
--
Mvh,
Endre
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
