On Sun, 18 Nov 2001 12:01:11 -0600, Troy Moreland wrote:
>Can someone tell me how to get around the following problem:
>
>I am using sessions to store a person's ID and password that they
>authenticate with at the start page. The entire web site is secured
>this way. The problem is that hitting the back key often gives the
>"This page has expired, hit Refresh to Reload" kind of message. How
>can this be avoided? I've written the same application without
>sessions (unsecure obviously) and I don't get asked for refreshes at
>all.
>
>Thanks, Troy Moreland
>
Hi Troy,
AFAIK, there are two solutions to this problem.
1. Switch from the POST to GET method when you are supplying your
information for your site. This is a problem related to the way POST
messages are handled (its sent as a separate data package in fact) by
the web browser, and with get, this is of course in your URL and thus
also handled by default
2. Edit your php.ini file and set the cache limiter to nothing
(session.cache_limiter=;). This will fix the problem for all your
POST forms, for all web pages. If you only want this done for part of
your website, do it with headers instead, eg:
session_start();
header("Cache-Control: ");
header("pragma: ");
blah blah blah...
Hope this helps! ;)
Cheers,
Egil
-=//
Egil Helland / IKON AS - MCSE, Internet, Intranet
mailto:[EMAIL PROTECTED] http://egil.net
//=-
--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
