The no-cache does not always work. For preventing caching, if the page
is ASP (or make it ASP), add the following lines at the beginning of the
document.
<%@ Language = VBscript %>
<%
Response.Expires = 60
Response.Expiresabsolute = Now() - 1
Response.AddHeader "pragma","no-cache"
Response.AddHeader "cache-control","private"
Response.CacheControl = "no-cache"
%>
I am not familiar with cpanel. For folks with protected pages or site
areas (not intranets), the usual method is to prompt the user to a login
page to authenticate, then store the authicated key in a cookie or a
session varibable and then redirect to the reuested page. Then when a
user requests another protected page, the server/page checks whether the
user is authenticated looking for the key. If the answer is yes, it
serves the potected page, if not it reditrects back to the login page.
For example yahoo, uses cokies.
For your example, if the no-caching does not work, you can have the
authentication page immediatley redirect to a page that alwasy ridrects
to another page. eg. login page -->alwaysredirect.asp-->somepage.
If the user clicks the back icon at somepage it will bring back to
somepage again. Sopticates user can get aroudn this. But msot folks
don't know how.
...PC