Clearing Browser History using JavaScript

[codeexploiter]

Hi Folks,

Is it possible for us to clear/erase the contents of the Client's Browser history?

Rather only one entry which is associated with my site?

I want to restrict the user going back to a particular page using the 'Back' button in the browser

Thanks in Advance

Code Exploiter

[mwinter]

Is it possible for us to clear/erase the contents of the Client's Browser history?

No.

Rather only one entry which is associated with my site?

Still no.

I want to restrict the user going back to a particular page using the 'Back' button in the browser

You can't. Write whatever system it is that you're developing to cope with that eventuality.

Mike

[Twey]

If you use window.location.replace("newpage.htm"), the user agent will be sent to newpage.htm, which will replace the current page in the browser's history. This is generally a bad idea, except for:

1. Redirect pages that might cause the user to become "stuck";
2. Splash-type pages that contain no content the user might want to revisit.

[mwinter]

If you use window.location.replace("newpage.htm"), the user agent will be sent to newpage.htm, which will replace the current page in the browser's history.

Which introduces a scripting dependency. That should mean you provide a non-scripted fallback:

<a href="..." onclick="location.replace(this.href); return false;">...</a>

However, this still means that some users can use the back button.

So, as I said, it needs to be accomodated server-side.

Mike

[MayISuggest]

Hi,

A possible solution could be adding this simple script in the beginning of the page you don't want the user to goback to.

<script language="javascript" >
history.go(1); /* undo user navigation (ex: IE Back Button) */
</script>

[djr33]

That wouldn't allow them to see the page ever.

As for the original question... no, you can't delete/change/etc files that are on the users' computers. Simple as that.

You could do a cookie/IP/session/etc tracking with server or client side programming, or try what twey suggested.

[codeexploiter]

Yes actually this issue had resolved long time but I missed to post a message that it is resolved.

I am really sorry about it.

regards

[Ges]

Hello all,

Firstley, interfering with ANY clients' computers is both unprofessional and insulting to say the least. As a web designer your top priority is to ensure the TOTAL SAFETY of ALL your visitors/guests. What rights do you have to attempt to do such things on anyones computer using a CLIENT SIDE script? Ever heard of trusted sites in your browser?

I agree with MWINTER in that he points out the problems associated with this sort of behaviour - which can only be described as 'internet hooliganism/vandalism'. Are'nt there enough hackers out there without adding to the list?

The professional/ethical way to restrict unwelcome visitors is to use a SERVER SIDE IP BANNING script - available in PHP from various sources. That way you can at least restrict access from a particular computer without interference with the clients equipment.

Internet security is of utmost importance to all of us but safety can be achieved without resorting to underhand methods. Try visiting;

http://www.astalavista.com/

and;

http://www.astalavista.net

These people are PAID to test internet systems - from communication to internet sites for banks etc. I have been a member for a number of years and find the articles very interesting. A lot can be learned from them.

I apologise if I sound a bit harsh but so is life and the truth often hurts.

Regards,
Ges.

[codeexploiter]

What rights do you have to attempt to do such things on anyones computer using a CLIENT SIDE script? Ever heard of trusted sites in your browser?

As a web developer what right do you have to set a cookie in a clients machine without their permission?

Though cookies doesn't contain any malicious contents (as far as i knew) still it is wrong to set a cookie in a visitor's machine without their consent.

I am also sorry if i sound harsh.

I had already mentioned that I've got the answers already and my issue has already resolved.

[djr33]

The point is valid, though.
cookies are designed to be used, and the user can block them if s/he desires.

However, deleting something they would expect control of, the history for example, is bad.