Bug #78740
closed
Backend login not possible with different urls
Added by Tobias Hüske over 7 years ago.
Updated over 5 years ago.
Category:
Backend JavaScript
Description
The backend login in TYPO3 8 (tested with 8.3 and 8.4) is not possible when trying to perform from different urls after the cache is warmed up.
Bug is reproducible as described:
1) Make a clear TYPO3 installation
2) Try to perform a login with a domain which matches the following scheme: typo3.randomnumber.defaulturl.de/typo3 => Login is working
3) Now try to perform a login with the following: randomnumber.defaulturl.de/typo3/typo3 => Login is not working
The JavaScript files (RsaEncryptionModule.js, Lang.js, Login.js and UserPassLogin.js) are not loaded correctly which causes that the login is not possible.
After clearing the cache (typo3temp/var/Cache), randomnumber.defaulturl.de/typo3/typo3 is working but typo3.randomnumber.defaulturl.de/typo3 is not.
Versions prior to 8 don't have the described behavior.
- Status changed from New to Needs Feedback
Hi!
I tried to reproduce that with latest master and the following domains:
123.kleindev
t3.123.kleindev
t3.456.kleindev
I was able to log into the BE with any domain in any order without any issue.
Can you check what the browser's network panel says about the JS files not being loaded?
Maybe it's the trustedHostPattern? See issue #59030 for details...
- Status changed from Needs Feedback to Closed
No feedback since 90 days > closing.
If you thin that this is the wrong decision or experience the issue again, then please reopen it or open a new issue with a reference to this one. Thank you.
- Status changed from Closed to Accepted
Background:
- typo3.example.com/typo3
- example.com/installdir/typo3
both pointing to the same doc root
Production Context enabled (important!).
Results in this bug.
- Status changed from Accepted to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF