| Summary: | Session management with http_refresh | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | Christoph Burgmer <chrislb> |
| Component: | general | Assignee: | Konqueror Bugs <konqueror-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | adawit, finex |
| Priority: | NOR | Keywords: | triaged |
| Version First Reported In: | 4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Christoph Burgmer
2006-04-21 15:56:58 UTC
Yes, it's a bug, but one that looks far too tricky to solve and too corner-case for the trouble it would be to implement the solution. One attribute that saves the last session's URL as long as the tab isn't touched with a new URL? I know it's a seldom case, but we want a software that's trustable in all cases. That's why I'm using this kind of software. Exactly: save the original URL as long as the tab wasn't touched. But what defines a "touch"? Maximising and viewing the tab? Scrolling the page? Changing tabs? What if there is only one tab? The simple fact of Konqueror getting focus? Touching for me would mean fetching a new url, but I guess that's not the clearest solution either. Is it possible to save the history in that case, so the user at least is able to go back? Possible in means of hassle-free. How is konqueror 4 managing profiles? Eventually could you tell me how to test this behaviour? Exactly what webisite could cause this? Thanks a lot. If you want to reproduce this, I guess you could setup a local webserver, point your browser to it, then log out of kde, change your webserver to redirect to another target and then log back in. If you finally log out a second time konqueror now should only save the latest target, i.e. the redirected one. This bug is more than two years old. Meanwhile Konqueror in KDE 4 comes with "Undo closed tab" which means that there is some code saving the complete history of the tab, something what would be the foundation of the last feature proposition done here by me. Furthermore as the only feasible solution (as in my eyes) to the initial problem is a bigger change in functionality it would be useful if a developer could comment of its merit and the will to implement that. Otherwise this bug should maybe just be closed as WONTFIX. To repeat the solution: "On logout save the whole current tab history for all tabs and restore it on log in." Thanks. (In reply to comment #7) > This bug is more than two years old. Meanwhile Konqueror in KDE 4 comes with > "Undo closed tab" which means that there is some code saving the complete > history of the tab, something what would be the foundation of the last feature > proposition done here by me. > > Furthermore as the only feasible solution (as in my eyes) to the initial > problem is a bigger change in functionality it would be useful if a developer > could comment of its merit and the will to implement that. Otherwise this bug > should maybe just be closed as WONTFIX. > > To repeat the solution: > "On logout save the whole current tab history for all tabs and restore it on > log in." This is exactly what Konqueror save session does. It saves the current history for all tabs. Restored or otherwise. What is probably happening here is that the http cache is interfering and send you the old page. Does turning off page caching resolve the issue. IOW, this is a problem that should be reproducable in all browsers that save session information and not just Konqueror. Does disabling the cache solve the issue and is this still valid for Konqueror 4.8.4 or later? If not, please close the bug, otherwise update the version field. Thanks. 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 set the bug status 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! Dear Bug Submitter, 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! |