|
|
Posted by James on 09/30/43 11:14
I apologize in advance if I'm asking basic questions...
When you hit the back button, won't the browser just take the page
from the cache?
I haven't switched my POSTs to GETs and this is what I'm seeing.
I have a list of images. There are check boxes next to the images.
When the user checks images and clicks on a DELETE CHECKED link, a
new list is shown (minus the ones deleted.) When the user hits the
BACK button, I see the list again with checks next to the previous
images marked for deletion.
Just in case...
I tried to add the following header before any html output to force
the browser to not load from the cache and it didn't work.
header("Cache-Control: no-store, no-cache, must-revalidate");
-James
At 1:59 PM -0500 4/26/05, Greg Donald wrote:
>On 4/26/05, James <jtu@esidesign.com> wrote:
>> What have people done in the past to deal with states and such and
>> keeping these things straight when the user hits the BACK button?
>
>Use GET instead of POST for your form method. And if you need both
>methods just handle the incoming requests from the $_REQUEST array.
>
>
>--
>Greg Donald
>Zend Certified Engineer
>http://destiney.com/
>
>--
>PHP General Mailing List (http://www.php.net/)
>To unsubscribe, visit: http://www.php.net/unsub.php
--
Navigation:
[Reply to this message]
|