Re: flushing formdata / flushing the client to prevent resubmitting formdata ?

In article <11F2EE072E68D311AC5600508B555299C28DAB@nts2.samhoud.nl>, J.Wesbeek@DoWebWeDo.com (Jeroen Wesbeek) wrote: > Is there any way of preventing form-data being resubmitted after hitting > F5/refresh in your client? > > Ofcourse you can create a warkaround by giving a form a random number or > something and check > if this number has already been submitted in the script that handles the > form data, but I'd rather > see if there's a way to flush the client as soon as script is run which > processes this data. > > So.. is there some kind of HTTP header which you can send to the client to > make sure the data > won't get re-submitted after refreshing? You can send every no-cache header and expiration header you can get your hands on as well as a random (or uniqid(), even better). *MOST* folks won't be able to reload, but you'll need to catch the broken browsers. -- Richard Lynch | If this was worth $$$ to you, buy a CD US Customer Support Director | from one of the artists listed here: Zend Technologies USA | http://www.L-I-E.com/artists.htm http://www.zend.com | (this has nothing to do with Zend, duh!)