-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] 404 errors when trying to reach Dashboard's admin section #194
Comments
replace Line 88 in 603060a
with ) else (
<dispatch xmlns="http://exist.sourceforge.net/NS/exist">
<forward url="login.html">
<cache-control cache="no"/>
<set-header name="Cache-Control" value="no-cache"/>
</forward>
</dispatch>
) will forward to the login page (infamously known from #156) but fix the 404 error and will let you access the admin section. ) else (
<dispatch xmlns="http://exist.sourceforge.net/NS/exist">
<redirect url="index.html"/>
</dispatch>
) could be what we are really after, redirecting users that are "effectively" logged in but not as administrators back to the normal launcher view with the possibility to log in. |
@line-o yep, please do so. Would go with variant 2. |
@line-o Thanks for fixing this - and, in particular, of your own accord! |
Describe the bug
Many users have reported that after upgrading to Dashboard v2.0.8 (the latest version, which ships with eXist 5.3.0), the admin section of Dashboard yields persistent 404 errors—rendering the admin functions of Dashboard inaccessible. Clearing cookies and cache may (or may not) temporarily relieve the problem, but it returns under common circumstances, involving logging into other eXIst apps like eXide and restarting eXist.
Expected behavior
There should not be a 404 error when using Dashboard's admin section.
To Reproduce
Discussion
Step 2 sets a cookie, like this:
After restarting in step 4, this cookie persists.
Only when you delete this
org.exist.login
cookie is Dashboard's admin section accessible again. There are a few methods to delete the cookie:response:set-cookie("org.exist.login", "", xs:duration("PT1S"), false(), "localhost", "/exist")
in eXide.Thus, it appears that something about the stale
org.exist.login
persistent login cookie throws off Dashboard and triggers this 404.Context (please always complete the following information):
Additional context
conf.xml
? noneThe text was updated successfully, but these errors were encountered: