Details
-
Bug
-
Resolution: Fixed
-
Major
-
2.0 Final
-
None
-
Windows XP
Description
Hallo,
I think I found a new bug with a failing second access to a secured page on public instance.
What I did:
1) first, I created a deny for a page (let's call it ONE) in author and activated it
2) second, I created a user and a password and activated this user
3) to be sure, I restarted public
4) with a fresh browser instance (all cookies and offline stuff deleted) I surfed to that secured page ONE, the enforced login shows up
5) I entered the newly created user and the password so the page ONE was successfully shown
6) I chose a different page from the navigation
7) I navigated back to the page ONE but the default page as configured by ResourceNotAvailableURIMapping only was shown
THE EFFECT: from then on, no second access to the secured page is possible. Except for public's restart.
MY WORKAROUND as proposed by Ralf Hirning:
- Turn off caching for the secured page
Wonder what you guys will come up with ![]()
Regards, Mirko