I consistently use the POST method when submitting a form to a PHP script.
I seldom use GET.
-Original Message-
From: olinux o [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 03, 2001 1:34 PM
To: [EMAIL PROTECTED]
Subject: Re: [PHP-DB] Warning: Page has Expired
I have the same
and set it to session.cache_limiter = nocache
HTH 8^D
Dave
-Original Message-
From: olinux o [mailto:[EMAIL PROTECTED]]
Sent: 03 September 2001 19:34
To: [EMAIL PROTECTED]
Subject: Re: [PHP-DB] Warning: Page has Expired
I have the same troubles. I believe that the only
solution is to use GET rather than POST
POST is no more secure, realistically, than the GET method. Both pass
data around in plain-text form.
In a perfect world web browsers wouldn't cache pages which were POSTed to
as the HTTP specification says. At least, that's my understanding of it.
Browsers -are- free to cache GET'ed pages
I have the same troubles. I believe that the only
solution is to use GET rather than POST as your FORM
METHOD. There may be another way, but this may work
fine, as long as you are not working with
passwords/sensitive info.
olinux
--- Mad Nas [EMAIL PROTECTED] wrote:
Hi All
I'm using PHP 4
look in php.ini (or whatever the Linux equivalent is) for
session.cache_limiter and set it to session.cache_limiter = nocache
HTH 8^D
Dave
-Original Message-
From: olinux o [mailto:[EMAIL PROTECTED]]
Sent: 03 September 2001 19:34
To: [EMAIL PROTECTED]
Subject: Re: [PHP-DB] Warning
How can I do away with this error when the BACK button
is pushed?
Thanks,
olinux
__
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
--
PHP Database Mailing List
I've setup a members directory in mysql that is searchable via different field and I
limit the number of records.
I use session variables to remember the number of records to display, what the
starting record is, what the
search string and search fields are. At anytime a user can click on an
