Bug 126024 - Session management with http_refresh
Summary: Session management with http_refresh
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 4.0
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2006-04-21 15:56 UTC by Christoph Burgmer
Modified: 2018-10-27 04:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Burgmer 2006-04-21 15:56:58 UTC
Version:           3.5.2 (using KDE KDE 3.5.2)
Installed from:    Debian testing/unstable Packages
OS:                Linux

If konqueror is reopened from a saved session and the reopened websites contain a http_refresh meta tag konqueror follows it and if the browser tab is untouched saves the redirected page for the next session.

As this seems a logical thing to do, it can cause serious annoyment - especially with a portable computer: If for example a different connection type is chosen during session change and the new gateway forces all urls to redirect to one certain page as it is commonly found with wlan access points konqueror will just save this redirected page thus destroying all links.

I marked this as bug not whishlist, as users would expect konqueror to bring up their last pages in any case, without looking on the implications.
Comment 1 Thiago Macieira 2006-04-24 09:26:01 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.
Comment 2 Christoph Burgmer 2006-04-24 10:37:57 UTC
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.
Comment 3 Thiago Macieira 2006-04-25 00:43:16 UTC
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?
Comment 4 Christoph Burgmer 2006-04-25 02:00:37 UTC
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.
Comment 5 FiNeX 2008-05-06 14:13:10 UTC
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.
Comment 6 Christoph Burgmer 2008-05-11 12:35:07 UTC
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.
Comment 7 Christoph Burgmer 2008-10-22 10:33:12 UTC
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.
Comment 8 Dawit Alemayehu 2011-11-30 06:24:30 UTC
(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.
Comment 9 Janek Bevendorff 2012-06-18 19:45:51 UTC
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.
Comment 10 Andrew Crouthamel 2018-09-23 02:36:36 UTC
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!
Comment 11 Andrew Crouthamel 2018-10-27 04:04:13 UTC
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!