You probably know this scenario: Load some page (mostly the one which requests some sql query on the server, e.g. search) in web browser (e.g. Firefox) and you click on some item. Then you click back and you get:
Code:
Do you know how to workaround it ? Somehow force Firefox to cache all pages and never expire them (at least for current session).
Old good Proxomitron (web proxy with filter) has a rule for it (see "Kill anti-cache" at http://homepage.usask.ca/~ijm451/prox/help/help/Default%20Web%20Filters.html). But this project is dead about 9 years
Any idea how to force Firefox to ignore
Code:
command ?

Are you pressing the back button in your browser? If so, that's a security measure from the website.

Yes, and that's exactly what I want to override.

It looks like Firefox itself doesn't have a setting for that, but this thread may be relevant to you. I hope that your reasons for the override are more legitimate than this poster.
http://superuser.com/questions/275377/ignore-no-cache-header

I didn't know mp3 could be downloaded this way. I wanted it just to speed-up browsing and sometimes to save data (e.g. text in web mail if connection crashed while sending).

Perhaps you should be using a webmail client that saves drafts? I know that SquirrelBox and RoundCube do, and of course gmail does. You could also consider an offline web client? I blame whatever website is declaring the no-cache pragma rather than your browser on this issue.

It is indeed a server side issue. The page expires pretty much as soon as you navigate away. It's not a cache related message as far as I'm aware. But I'm not entirely educated on no-cache and page expiration periods.

Easiest way is open whatever you click in a new tab, then you don't have to hit back at all.

I find that pretty annoying, too—I mostly encounter it on sites that use https and have a web search of some kind. Pretty stupid to configure the server like that. Nearly anything that breaks the Back button in my browser tends to piss me off, though, including 0-second redirections and POSTDATA crap.

The local proxy solutions sound interesting, though probably only worth it if you encounter that a lot. Opening stuff in new tabs does sound the easiest, but I sometimes forget to do that (and it doesn't work if the site is really stupid and uses Javascript for all the links ).