[opensuse] FF 35 woes on 13.1 (prior search results NOT available when 'back' used)
All, This is frustrating. I use startpage. In all prior versions of Firefox, I could preform a search, follow a link, then press <back> to return to my search results. No I get this damn: Document Expired This document is no longer available. The requested document is not available in Firefox's cache. As a security precaution, Firefox does not automatically re-request sensitive documents. Click Try Again to re-request the document from the website. [ Try Again ] Jesus this is a pain. How can I tell FF 35 to please behave like all prior versions of FF and just show my search results again when I press back?? I don't want to have to click multiple buttons and confirm resends just to see them again. What in about:config controls this behavior? I've searched settings, and once again with Mozilla, this new 'feature' appears to be more of a 'bug' for some -- because, again, there is no way to TURN IT OFF. What says the braintrust? What's the trick to get usable search results back? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/03/15 00:40, David C. Rankin wrote:
All,
This is frustrating. I use startpage. In all prior versions of Firefox, I could preform a search, follow a link, then press <back> to return to my search results. No I get this damn:
Document Expired
This document is no longer available.
The requested document is not available in Firefox's cache.
As a security precaution, Firefox does not automatically re-request sensitive documents. Click Try Again to re-request the document from the website.
[ Try Again ]
Jesus this is a pain. How can I tell FF 35 to please behave like all prior versions of FF and just show my search results again when I press back?? I don't want to have to click multiple buttons and confirm resends just to see them again.
What in about:config controls this behavior? I've searched settings, and once again with Mozilla, this new 'feature' appears to be more of a 'bug' for some -- because, again, there is no way to TURN IT OFF.
What says the braintrust? What's the trick to get usable search results back?
I started seeing this a while back too. My second thought (my most immediate thought was 'bollocks') was that perhaps this was a deliberate change, given that Startpage is supposed to present results unbiased from other sources, i.e. maybe you'd want to see 'fresh' results rather than ones that are reliant on a previous search. Maybe it's just a (over-zealous) security setting? I doubt that's the case, but it did cross my mind. And although it would seem likely that it's Firefox that changed something since it occurs with one version and not another, I guess it's also possible that the problem exists in the way Startpage has coded the page, and that it only manifests itself in the latest FF version. Anyway, here's an bug that relates to it: https://bugzilla.mozilla.org/show_bug.cgi?id=1060082 which is also linked from https://bugzilla.mozilla.org/show_bug.cgi?id=1065234 Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/28/2015 06:15 PM, Peter wrote:
I started seeing this a while back too. My second thought (my most immediate thought was 'bollocks') was that perhaps this was a deliberate change, given that Startpage is supposed to present results unbiased from other sources, i.e. maybe you'd want to see 'fresh' results rather than ones that are reliant on a previous search. Maybe it's just a (over-zealous) security setting? I doubt that's the case, but it did cross my mind.
And although it would seem likely that it's Firefox that changed something since it occurs with one version and not another, I guess it's also possible that the problem exists in the way Startpage has coded the page, and that it only manifests itself in the latest FF version.
Anyway, here's an bug that relates to it: https://bugzilla.mozilla.org/show_bug.cgi?id=1060082 which is also linked from https://bugzilla.mozilla.org/show_bug.cgi?id=1065234
Peter
It is another Mozilla gift. I found another couple of threads on it. See: https://support.mozilla.org/questions/1047023 https://support.mozilla.org/en-US/questions/1010942 It does seem that there was a change, and true-to-form, there seems to be nothing provided that lets you select/configure this behavior to regain traditional operations. 1010942 mentions Tools->Options->Override Automatic Cache Management, but this must be a windows or dev option as it is not present in FF35. I have also searched about:config for 'override', 'cache', 'management', etc.. but have not found a probable match. I'll keep looking. If devs would just remember that the new gee-whiz way they want to do it, might not be the way everybody wants to do it, there would be far fewer issues and complaints. I'm all for new features. But a 'new feature' to one is a horrible inconvenience to someone else. Linux has traditionally been about user choice, and it has been furthered by providing user-options to configure things as they like. The old adage that: "a new feature is a bug if it cannot be turned off" still rings true. Don't get me wrong, I'm a mozilla supporter and user since 0.x or 1.x days, but since this silly version race from 3.x -> now version 35+ has taken place, it seems like the new crop of devs have completely forgotten these lessons. Thanks for your help, I'll keep digging and if I find a solution, I'll post it here. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin composed on 2015-02-28 21:08 (UTC-0600):
seems like the new crop of devs have completely forgotten these lessons.
Forget what was never learned to start with? The web is more complex than it used to be, and so have grown browsers. http://archive.mozilla.org/pub/mozilla.org/firefox/releases/1.0/linux-i686/e... is 7.8M. http://archive.mozilla.org/pub/mozilla.org/firefox/releases/36.0/linux-i686/... is 46M. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/03/15 04:08, David C. Rankin wrote:
On 02/28/2015 06:15 PM, Peter wrote:
I started seeing this a while back too. My second thought (my most immediate thought was 'bollocks') was that perhaps this was a deliberate change, given that Startpage is supposed to present results unbiased from other sources, i.e. maybe you'd want to see 'fresh' results rather than ones that are reliant on a previous search. Maybe it's just a (over-zealous) security setting? I doubt that's the case, but it did cross my mind.
And although it would seem likely that it's Firefox that changed something since it occurs with one version and not another, I guess it's also possible that the problem exists in the way Startpage has coded the page, and that it only manifests itself in the latest FF version.
Anyway, here's an bug that relates to it: https://bugzilla.mozilla.org/show_bug.cgi?id=1060082 which is also linked from https://bugzilla.mozilla.org/show_bug.cgi?id=1065234
Peter
It is another Mozilla gift. I found another couple of threads on it. See:
https://support.mozilla.org/questions/1047023 https://support.mozilla.org/en-US/questions/1010942
It does seem that there was a change, and true-to-form, there seems to be nothing provided that lets you select/configure this behavior to regain traditional operations.
1010942 mentions Tools->Options->Override Automatic Cache Management, but this must be a windows or dev option as it is not present in FF35. I have also searched about:config for 'override', 'cache', 'management', etc.. but have not found a probable match.
I'll keep looking. If devs would just remember that the new gee-whiz way they want to do it, might not be the way everybody wants to do it, there would be far fewer issues and complaints. I'm all for new features. But a 'new feature' to one is a horrible inconvenience to someone else. Linux has traditionally been about user choice, and it has been furthered by providing user-options to configure things as they like. The old adage that: "a new feature is a bug if it cannot be turned off" still rings true.
Don't get me wrong, I'm a mozilla supporter and user since 0.x or 1.x days, but since this silly version race from 3.x -> now version 35+ has taken place, it seems like the new crop of devs have completely forgotten these lessons.
Thanks for your help, I'll keep digging and if I find a solution, I'll post it here.
Not a solution but a simple workaround. It may run against your preferred 'workflow' but you could right-click links on search results pages to open in a new tab, or just drag them to an empty part of the tab bar. I find myself increasingly doing that in various search engines because for one reason or another, going back presents annoying quirks. Not just the Startpage issue you bring up, but on DuckDuckGo for example I kept finding that it would skip back to an irrelevant part higher up the results page and I'd have to scroll back down. Another search engine, I forget which, had an irritating delay in page load when navigating back. From time to time you also run into that pitiful design of some miserable web developers worthy of a good chainsaw unboxing whereby clicking Back automatically redirects to the current page and tries to lock you in. Being able to just close a tab, or switch back to the results still open in another tab, seems more useful to me a lot of the time. Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/28/2015 09:30 PM, Peter wrote:
Not a solution but a simple workaround. It may run against your preferred 'workflow' but you could right-click links on search results pages to open in a new tab
Yes, this is EXACTLY what I'm trying to avoid. I cannot stand opening/closing multiple tabs/windows/etc.. (I'm old and senile I guess, but definitely stuck in my ways). Ever since I began using FF with search, I've used a single page. That way I keep a clean browser interface with the tabs I am working with open and in-view. The open-in-new-tab causes the tabs to scroll out of view, etc.. and that is what I try to avoid. It looks like there is a problem with mozilla's implementation of their 'respect the no-cache header...' This security enhancement seems to be functioning precisely in the 'inverse' manner it was intended to. It also effect form completion, etc. in this manner. I'd like to say, "it will be fixed soon in the next release", but then the anxiety of 'what new will be broken' makes me not look forward to any new FF releases..." Worst case, I can always drop back to MozillaFirefox-31.1.0-42.1.x86_64.rpm (which is what I did after 33.0-46.2 came out. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/28/2015 10:16 PM, David C. Rankin wrote:
On 02/28/2015 09:30 PM, Peter wrote:
Not a solution but a simple workaround. It may run against your preferred 'workflow' but you could right-click links on search results pages to open in a new tab
Yes, this is EXACTLY what I'm trying to avoid. I cannot stand opening/closing multiple tabs/windows/etc.. (I'm old and senile I guess, but definitely stuck in my ways). Ever since I began using FF with search, I've used a single page. That way I keep a clean browser interface with the tabs I am working with open and in-view. The open-in-new-tab causes the tabs to scroll out of view, etc.. and that is what I try to avoid.
It looks like there is a problem with mozilla's implementation of their 'respect the no-cache header...' This security enhancement seems to be functioning precisely in the 'inverse' manner it was intended to. It also effect form completion, etc. in this manner.
I'd like to say, "it will be fixed soon in the next release", but then the anxiety of 'what new will be broken' makes me not look forward to any new FF releases..."
Worst case, I can always drop back to MozillaFirefox-31.1.0-42.1.x86_64.rpm (which is what I did after 33.0-46.2 came out.
Bug filed on the blocking re-request of "non-sensitive" documents. https://bugzilla.mozilla.org/show_bug.cgi?id=1138291 The problem is the mozilla developers have virtually NO way to determine if a document is "sensitive" (and re-request should be blocked) or "non-sensitive" (where re-request should be allowed). Therefore in our now non-beta test periods for the rapid-fire/rabbit pellet release cycle, it appears what the developers chose to do was to just "block them ALL"... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/28/2015 06:40 PM, David C. Rankin wrote:
All,
This is frustrating. I use startpage. In all prior versions of Firefox, I could preform a search, follow a link, then press <back> to return to my search results. No I get this damn:
Document Expired
This document is no longer available.
The requested document is not available in Firefox's cache.
As a security precaution, Firefox does not automatically re-request sensitive documents. Click Try Again to re-request the document from the website.
[ Try Again ]
Instead of clicking with the left mouse button, use the middle button to open a new tab. That way you always have the original search tab intact with its content. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
David C. Rankin -
Felix Miata -
Ken Schneider - openSUSE -
Peter