[m a d r a]

does anyone else have this gripe with safari? - this is an easily reproducible one on these very fora:

like a dutiful supplicant you do a search before posting and safari brings up the list of matches... so you click one and read the thread to see if it's relevant.... no. so hit the back button to return to the page of search results to select another.... safari pops up that annoying "are you sure you want to resubmit the form data...?" alert. when you OK this, you can see that your original search is being performed over again, thus wasting valuable time, bandwidth, patience.

why does safari do this? i'm not resubmitting the [search] form data. i'm just clicking the back button to return to a static page of search results. i've seen this happen with other sites too. it doesn't happen all the time but often enough to be a major irritant. seems if you've arrived at page C via a form on page A and then a static page B, hitting the back button causes safari to think you're resubmitting the form on page A again.

anyone else noticed this?

[dr. zoidberg]

i would think that this is dependent on the way how the search-result is generated, so probably it's not exactly safaris fault. results pages are not necessarily static pages, but often scripts that rely on parameter feed. did you check it with other browsers if it´s different with them on those particular forums?

[Apfhex]

Safari is the only browser I've seen do this. It bugs me too.

In some cases I can see why this warning is appropriate, but in the MaNN example given, it shouldn't do it.

Well, Safari DOES seem to like to reload data a lot (i.e. when you "Download Image to Disk" it re-downloads it).

[schk]

this annoys me as well, i've only had it happen to me with safari. browsing back on the results of a search script on a msg board should not prompt for a resubmission of the search keywords, it should just use the cache.

[tr]

Originally posted by schk:
this annoys me as well, i've only had it happen to me with safari. browsing back on the results of a search script on a msg board should not prompt for a resubmission of the search keywords, it should just use the cache.

yeah, i too am annoyed at this. i don't know why it doesn't use the cache; it seems every other browser i use does this. safari always wants to reload data.

tr

[LeeG]

Man, I thought I was the only one this drove crazy. I have had to make myself get in the habit of control-clicking and opening in a new tab MacNN serach results because of the 'resend' data thing - I hate it...

Lee

[LeeG]

I have submitted this to apple, you all should as well-

Lee

[Joel]

Originally posted by LeeG:
Man, I thought I was the only one this drove crazy. I have had to make myself get in the habit of control-clicking and opening in a new tab MacNN serach results because of the 'resend' data thing - I hate it...

Yes, this annoys me as well. I still forget to open search links in a new tab sometimes. Just for the record, command-clicking a link automatically opens the link in a new tab without having to control-click and select "Open Link in New Tab" (just for anyone who hasn't caught that yet).

-Joel

[Gul Banana]

Safari, despite having a very efficient RAM cache, does seem to adore dynamic reloading and ensuring you have the latest version of a page. It really is designed for fast broadband, I think.

[tonton]

It's because of Safari's refusal to retrieve pages and data from cache.

[Love Calm Quiet]

I'm with you about the annoyance - seems like it should be an *option*.

After all, there is a reason to alert someone. On a very dynamic site (like MacNN or Amz for example) it may be good to consider *whether* to go back to the most recently cached material or to a re-searched display.

The problem is sometimes I *don't want* a re-searching even if I know the results have changed... I want to review the *previous* results (not any revised status).

Anybody know WHAT TYPE of search processes get-vs-don't get cached. Amazon's *does*, fortunately: thus I can go back to the previous snapshot of my shopping cart even after I've deleted an item and find the (?mistakenly?) deleted item.

With my own PHP/MySQL pages I find that I can *not* do that. Is it diff for php / asp / etc?