parse-community / parse-community/parse-dashboard
Redirect after login leads to incorrect path
Open
Nobody has claimed this yet.
type:bug
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.
Issue Description
When the login session of Parse Dashboard has expired, the redirection contains an incorrect URL with an additional slash.
Steps to reproduce
- Open a new browser window, log in to Parse Dashboard and navigate to the
_Userclass. - Delete all website data incl. cookies for the dashboard website in the browser settings.
- Reload the website.
- Browser URL shows login page with URL:
https://example.com/login?redirect=/apps/app-name/browser/_User - Open a new browser tab in the same browser window, copy paste the URL above and log in.
- Reload the first tab that shows the login page.
- A redirection to URL
https://example.com//apps/app-name/browser/_Useroccurs which leads to a 404 site.
Actual Outcome
The redirection URL in step 7 above contains an additional slash.
Expected Outcome
The redirection URL should not contain the additional slash.
Environment
Dashboard
- Parse Dashboard version:
6.0.0 - Browser (Safari, Chrome, Firefox, Edge, etc.):
Safari
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue. Start by reproducing the expired-session flow and tracing the login redirect handling in Parse Dashboard; done means redirecting to the requested path without the additional slash and avoiding the 404 URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100