Version: 0.5.0 (using KDE 4.4.4) OS: Linux When there are problems with internet connection and page loading fails and shows "Try Again" button - after pressing "Try Again" url parameters (like PHPBB topic IDs) are lost. Reproducible: Always Steps to Reproduce: 1. Open any PHPBB page. 2. Shut down internet connection. 3. Open any page in new tab. 4. Make internet connection available again. 5. Press "Try Again" button. Actual Results: You will see the url without paremeters and message about wrong page or something like that. Expected Results: The real page will be loaded and all parameters preserved. OS: Linux (x86_64) release 2.6.34-12-default Compiler: gcc
I can confirm this too with the latest rekonq mainline.
*** Bug 254722 has been marked as a duplicate of this bug. ***
found the culprit for this bug: Line 598 in webpage.cpp QString urlString = Qt::escape(reply->url().toString(QUrl::RemoveUserInfo | QUrl::RemoveQuery | QUrl::RemovePath));
Cannot backport to reKonq 0.6.x ?
(In reply to comment #4) > Cannot backport to reKonq 0.6.x ? Yes, as soon as we fixed it.
We need to cut the url because of a security issue, so it's not as easy as it looks like. We still try to fix that though.
Git commit 1d83ce109628cf28269a849abec9786b9e920c39 by Andrea Diamantini. Pushed by adjam into branch 'master'. This evening I started working again on this bug. I did all the tests against XSS and it seems ok. Hope it's true. CCBUG:217464 CCBUG:246355 M +7 -4 src/webpage.cpp http://commits.kde.org/rekonq/1d83ce109628cf28269a849abec9786b9e920c39
It seems working here now. Can someone please confirm it, so that we can close this bug (and backport to 0.6 as requested by Giovanni)?
I just updated to a more recent version of rekonq through this – https://launchpad.net/~yoann-laissus/+archive/rekonq-ppa – repository, which contains a daily build of 10 Februari. To try to reproduce the bug I followed the steps indicated by the bug reporter as closely as possible, I visited the phpBB forum – http://www.phpbb.com/community/index.php – of the phpBB community itself. I can confirm the bug did not occur.
OK :D Backporting today...