ძიება მხარდაჭერაში

ნუ გაებმებით თაღლითების მახეში მხარდაჭერის საიტზე. აქ არასდროს მოგთხოვენ სატელეფონო ნომერზე დარეკვას, შეტყობინების გამოგზავნას ან პირადი მონაცემების გაზიარებას. გთხოვთ, გვაცნობოთ რამე საეჭვოს შემჩნევისას „დარღვევაზე მოხსენების“ მეშვეობით.

ვრცლად

Any way (addon, about:config setting) to disable honoring no-cache

  • 1 პასუხი
  • 1 მომხმარებელი წააწყდა მსგავს სიძნელეს
  • 5 ნახვა
  • ბოლოს გამოეხმაურა guigs

Problem: There are a number of data driven sites whose admins use no-cache headers everywhere and pretty much every page is no-cache, each returning "Document has expired and is not cached" every time. To make things worse often these sites prevent you from opening pages in new tabs - basically any page that uses javascript to submit.

Typical scenario: You fill in a complex criteria search on a site. You submit it. You get a listing of 100 results. You click on the first one (can't open it in a new tab - uses javascript routine to open the page). Go back to look at the other search results - it is gone. Firefox did not cache it. Would you like to resubmit with several extra clicks and roundtrips to the server waiting for the server to run your search again? How about no? Sometimes this goes more than one level deep even - and it is maddening.

Workaround I am seeking: I want a way to control this behavior. Ideally per site - but could be globally too. Is there an advanced setting somewhere in about:config that will change this behavior? Or an addon that will do the job? Firefox had the data, and then threw it away because the server - not the user - told it to. I think as a basic matter of principle the user should be able to override webserver directives with his own browser running on his own computer.

Problem: There are a number of data driven sites whose admins use no-cache headers everywhere and pretty much every page is no-cache, each returning "Document has expired and is not cached" every time. To make things worse often these sites prevent you from opening pages in new tabs - basically any page that uses javascript to submit. Typical scenario: You fill in a complex criteria search on a site. You submit it. You get a listing of 100 results. You click on the first one (can't open it in a new tab - uses javascript routine to open the page). Go back to look at the other search results - it is gone. Firefox did not cache it. Would you like to resubmit with several extra clicks and roundtrips to the server waiting for the server to run your search again? How about no? Sometimes this goes more than one level deep even - and it is maddening. Workaround I am seeking: I want a way to control this behavior. Ideally per site - but could be globally too. Is there an advanced setting somewhere in about:config that will change this behavior? Or an addon that will do the job? Firefox had the data, and then threw it away because the server - not the user - told it to. I think as a basic matter of principle the user should be able to override webserver directives with his own browser running on his own computer.

ყველა პასუხი (1)