Re: Pulling my hair out over Netscape...

At 18:57 28.02.2001, Jackson, Michael said: --------------------[snip]-------------------- > Hello everyone... I've been developing a PHP app here for a while >now, and I have been encountering some most frustrating situations in which >something will work in IE but not Netscape. Some of this seems to be IE's >allowances for sloppy coding... :) But here's a new one. I have a form, >that if you were to submit this form once, it will always retain the same >value. I.E. I enter a value, hit OK. Then I press the back button. Then >I enter a DIFFERENT value, and hit OK. The SAME value is passed to the PHP >script! I'm using the post method, and I haven't found a way to shake this >yet! This is afflicting Netscape 4.7 and Netscape 6. Driving me crazy.... --------------------[snip]-------------------- I'm not sure if any values get passed to PHP at all... Netscape is very cache-inclined, so it is likely that you're seeing the cached output of your previous query. There are several methods to overcome this situation: (1) HTTP cache headers (see RFC2616, ftp://ftp.isi.edu/in-notes/rfc2616.txt): Cache-Control: no-cache (HTTP/1.1) Pragma: no-cache (HTTP/1.0) (2) Expires headers Expires: Sat, 1 Jan 2000 00:00 +0000 Or use the <META HTTP-EQUIV> fields. Note as a side effect that using the "Expires" header will keep a lot of search engines from indexing the result page. Another method is using a random value as SEARCH parameter, e.g. http://www.myhost.com/myapp.php?rv=0987412&...other parameters Your application must ensure that the random value is as random as possible. This makes the URL "unique" and will bypass any ill-behaved cache (it won't help if the user hits the back button, of course...) ...ebird >O Ernest E. Vogelsinger (\) http://www.1-at-web.at/ ^ ICQ# 13394035