-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Token removal from URL causing problems #516
Comments
Have the same problem with chrome but not after a reset change few thinks with LUCI and then locked out. First login needed two trys. |
Did you clear your browser caches to rule out redirects to stale urls and the like? |
Now that we don't have an url token anymore, '/cgi-bin/luci' becomes a valid url while cookies are restricted to only '/cgi-bin/luci/' and below. In order to ensure that the first request after login refers to a path covered by the authentication cookie, change build_url() to always append a trailing slash if we're referring to the base url. This should fix the login problems mentioned in #516. While we're touching the dispatcher, also remove remaining url token code. Signed-off-by: Jo-Philipp Wich <jow@openwrt.org>
Yes cleared , i test chrome last stable version with Windows and Linux google-chrome. Jow your commit 79383f5 fix it. |
Hmmm. I am reusing this issue to report bad news: I compiled a new version and tried to flash it, but flash window timeouts in the image upload & checksum calculation phase (after selecting firmware file and pressing "Flash image" button) with this error:
Luci should be up-to-date, as I manually applied the two commits after the previous build. It timeouts both in Firefox and in IE. |
I concur with this - flash upload hangs since last update. However, I can login OK now. |
After the change in 86326e0 I can login ok with Firefox, but not with IE11. The browser remains on the login screen.
If a page address is entered manually, it works and also navigation afterwards.
e.g. https://192.168.1.1/cgi-bin/luci/admin/system/startup
So that sounds like a browser-specific problem on the login page redirecting functionality.
The text was updated successfully, but these errors were encountered: