Version: 4.6.0 (using KDE 4.6.1) OS: Linux Hello, When a webserver server answer with the following HTTP header : Cache-Control no-cache, no-store, must-revalidate The browser should not keep the page in cache at all, and, for example, when going to another page and hitting the "back" button, it must reload the page. That's very usefull to force reload of an html form to avoid data inconsistence. Firefox does respect those headers and reload properly the page in such a case. Konqueror does not. Reproducible: Always Steps to Reproduce: 1/ Open a web page that anwser with Cache-Control no-cache, no-store, must-revalidate 2/ go to another page 3/ hit the back button Actual Results: The page is taken from cache Expected Results: It should had been reloaded from server to respect cache-control-policy
I tested this and kio_http does not cache any page for which the Cache-Control header contains no-cache. How exactly did you determine that Konqueror was not honoring this ? Also which web browser engine are you using ? You also do know that most web browsers, for the sake of speed, store the pages they rendered (outside the normal cache) for faster back/forward navigation, right ?
Hello, > How exactly did you determine that Konqueror was not > honoring this ? By looking to web server accesslog file. When using firefox I see that going back to page make an hit to the server. With Konqueror it does not. > Also which web browser engine are you using ? Konqueror with KHTML. I have just tested with Konqueror and WebKit and it correctly reload page like firefox. > You also do know that most web browsers, for the sake of speed, store the pages > they rendered (outside the normal cache) for faster back/forward navigation, > right ? Sure, but the cache-control header is set explicitely to disable that in some case (web forms for ex.).
(In reply to comment #2) > Hello, > > > How exactly did you determine that Konqueror was not > > honoring this ? > > By looking to web server accesslog file. When using firefox I see that going > back to page make an hit to the server. With Konqueror it does not. > > > Also which web browser engine are you using ? > > Konqueror with KHTML. I have just tested with Konqueror and WebKit and it > correctly reload page like firefox. > > > You also do know that most web browsers, for the sake of speed, store the pages > > they rendered (outside the normal cache) for faster back/forward navigation, > > right ? > > Sure, but the cache-control header is set explicitely to disable that in some > case (web forms for ex.). Great. Let us then reassign this to KHTML since both those engines use the same ioslave, kio_http, which is verified to be doing the right thing.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!