Training, Open Source computer languages
PerlPHPPythonMySQLApache / TomcatTclRubyJavaC and C++LinuxCSS 
Search for:
Home Accessibility Courses Diary The Mouth Forum Resources Site Map About Us Contact
 
For 2023 (and 2024 ...) - we are now fully retired from IT training.
We have made many, many friends over 25 years of teaching about Python, Tcl, Perl, PHP, Lua, Java, C and C++ - and MySQL, Linux and Solaris/SunOS too. Our training notes are now very much out of date, but due to upward compatability most of our examples remain operational and even relevant ad you are welcome to make us if them "as seen" and at your own risk.

Lisa and I (Graham) now live in what was our training centre in Melksham - happy to meet with former delegates here - but do check ahead before coming round. We are far from inactive - rather, enjoying the times that we are retired but still healthy enough in mind and body to be active!

I am also active in many other area and still look after a lot of web sites - you can find an index ((here))
Using the back button in Netscape

Posted by jill (jill), 31 October 2002
I have a search form which passes data to a results page written in php.  This results page has summary details, and the user can drill down on each record for more information.

If they drill down on one record and then click the back button to see the results list again, then in Internet Explorer 5, they do see the list.  But in Netscape 4.08, they get the message

'This document resulted from a POST operation and has expired from the cache. If you wish you can repost the form data to
recreate the document by pressing the reload button'

They can indeed press the reload button to see the list again.  However from a user friendliness point of view it would be better if they didn't have to.  Is there some code I could put in the results page which would make it reload if there was form data available?

TIA for any help.

Posted by John_Moylan (jfp), 31 October 2002
Could you use GET instead of POST?

That would put your data on the querystring and ensure that the form data is sent.

This assumes that its not sensitive data, but then again POST isn't secure either, If the data is sensitive you should be using https.....but I'm waffling.

POST sends the data as part of the http headers and you can't see it on the url. (www.test.php)

GET passes the data on the query string (www.test.php?method=GET)

Hitting back in whatever browser will work with a GET request.
jfp

Posted by admin (Graham Ellis), 1 November 2002
I would tend to extend your code to include a back function on the page rather than to rely on the browser - that way you have control.  It would be more work, but with careful use of functions to create / recreate completed boxes on forms it shouldn't be too bad.

A couple of cautions on Get:  (1) - the "yuk" factor os stuff appearing in the URL (2) - Any password field will be reaveled in the URL (3) Limit of 1K of information entered.    Oops - my "couple" has become a 3-some .....



This page is a thread posted to the opentalk forum at www.opentalk.org.uk and archived here for reference. To jump to the archive index please follow this link.

You can Add a comment or ranking to this page

© WELL HOUSE CONSULTANTS LTD., 2024: Well House Manor • 48 Spa Road • Melksham, Wiltshire • United Kingdom • SN12 7NY
PH: 01144 1225 708225 • FAX: 01144 1225 793803 • EMAIL: info@wellho.net • WEB: http://www.wellho.net • SKYPE: wellho