Bug #54776
closed
ssl proxy [only] for backend failed
0%
Description
..this makes me angry for a while:
backend: https://ssl-account.com/sub.domain.tld/typo3/
frontend: http://sub.domain.tld/index.php?id=xxx
--
[reverseProxyIP] = *
[reverseProxyHeaderMultiValue] = first
[reverseProxyPrefix] =
[reverseProxySSL] = *
[reverseProxyPrefixSSL] = /sub.domain.tld
--
..with this configuration i've following results:
backend over: https://ssl-account.com/sub.domain.tld/typo3/ > okay
frontend direct: "sub.domain.tld" and over root-id: > calls: https://sub.domain.tld/sub.domain.tld > NOT okay [!]
frontend over other id: sub.domain.tld?id=xxx > okay
if i try any other configuration the backend don't work!
~backend logins over ssl-proxies at other cms are more functional! :/
.loon
Updated by Mathias Schreiber almost 10 years ago
- Target version set to 7.2 (Frontend)
Updated by Benni Mack over 9 years ago
- Target version changed from 7.2 (Frontend) to 7.4 (Backend)
Updated by Susanne Moog over 9 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack about 9 years ago
- Target version changed from 7.5 to 7 LTS
Updated by Riccardo De Contardi almost 9 years ago
- Target version changed from 7 LTS to Candidate for Major Version
Updated by Alexander Opitz over 6 years ago
- Status changed from New to Needs Feedback
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (7.6.24 or 8.6.10)?
Updated by Riccardo De Contardi over 6 years ago
- Status changed from Needs Feedback to Closed
- Target version deleted (
Candidate for Major Version)
No feedback since the last 90 days => closing this issue.
If you think that this is the wrong decision or experience the issue again and have more information about how to reproduce your problem and a more detailed explanation of your use case, please reopen it or open a new issue with a reference to this one.
Thank you and best regards