I've stumbled upon the issue outlined here:
Internet Explorer 11 Back Button Javascript Behavior
While experimenting with various approaches on how to resolve the issue I noticed that if the TabProcGrowth registry-key is set to a value of DWORD=0 then IE11 seizes to cache all those webpages I noticed it caching before the aforementioned registry tweak. However, even if something like this is true I can't find any documentation which explicitly mentions this side-effect of setting TabProcGrowth to zero. The thought of putting my money on such an approach makes me feel uneasy so I would like to ask if there's anyone that can verify my claim in a well-informed manner (docs etc).
Quick footnote: Yes ... I'm aware that this registry setting is not the best idea in the world performance-wise, but for the sake of argument let's assume I'm desperate because I have no control over the webpages or the web servers that deliver them, so pulling tricks with http headers is a no-go for me. However when it comes to the client's registry, that, I can tweak. This is why I'm asking.