"Philip Ronan" <in*****@invalid.invalid> wrote in message
news:BE3E1EFF.2B7F6%in*****@invalid.invalid...
But why anyone would need to use the "BACK" button to return to a
previously submitted POST form? If the OP is trying to -- for example -- add several
similar items to a database, then it would be much better to submit the
form to the same URL and pre-fill it with the items submitted last time.
Relying on the BACK button as a means of retrieving stale data sounds like the
wrong way of doing things.
OK interesting comments Alan. Steering things back to the problem I was
originally trying to solve the following is the scenario.
1) Client uses a search web page to search for matching results in a MySQL
DB.
2) They are shown a list of matching results when submitting a search
(currently as POST)
3) They sometimes click in to view full details of a particular result.
----
4) Further to this they sometimes like to click back and then click to view
the full details of another particular result.
5) Sometimes they like to go back even further, going back to the original
search page and make some minor changes to the original search criteria they
put in (without putting it in all over again).
In IE (which client uses and probably wont change):
* When using POST in the search form at point 4, when pressing back they
either get Page Expired or it takes them back to the search page. If it does
go to the search page, all the search fields have been cleared
* When using GET, they can go back to the search results page and choose
another (Great). If they go back to the search page, all the search fields
are cleared (it like you have clicked on the search page link for the first
time - it even takes a while to load up)
Note that using Firefox, using the back button behaves much better, as a
human would expect it to, but not going to be easy to get client to use it
so need to look at IE solution.
Also because there are a lot of SEARCH fields, I was worried about using a
GET because I was worried that it would be too much information for a GET to
carry and feel more comfortable using POST because it is what I have always
done for form submissions.
So the ideal scenario is, I use POST on the search form, the user can go
back, and they actually see what they saw before they clicked the link. This
is what my client expects.
Also note: you may be tempted to criticise the initial design, but this DB
is inherited from another company and we have taken over management. Major
changes will come, but later, so looking for quick fixes.
Hope that spells it out a bit more clearly and I hope someone can spell out
a clearer quick answer for me or convince me that it is fine to use GET,
even when you have a very large number of form fields to submit with long
names.
Regards
Dave