Bug #84852

Reverse Proxy

Added by Boreas Media about 1 year ago. Updated 2 months ago.

Status:
New
Priority:
Must have
Assignee:
-
Category:
System/Bootstrap/Configuration
Start date:
2018-04-24
Due date:
% Done:

0%

TYPO3 Version:
8
PHP Version:
7.0
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

We have set up a reverse proxy and configured TYPO3 accordingly in Localconf.
reverseProxyHeaderMultiValue' => 'last',
reverseProxyIP' => 'xx.xx.xx.xx.xx',
reverseProxyPrefixSSL' => >'/intranet',
reverseProxySSL' => '*',

The URL in the browser is: domain.tld/intranet
This also works so far, but the backend of TYPO3 does not work at all after the login. It writes another "/intranet" every time..... Also the frontend does not work as soon as a login happens.
The URL to domain.tld/intranet/intranet/typo3/index.php?xxxxx is changed in the backend.
We solved it in such a way that we simply wrote a redirect in the htaccess. That if there is a "/intranet" in the URL, simply remove it. Nevertheless, we think that it is a TYPO3 error. Because now the following error is thrown in the backend when we want to edit a content element:
file_get_contents(/var/wwww/xxxx/html/typo3//intranet/typo3conf/ext/rtehtmlarea/Resources/Public/Css/Skin/jquery-ui-resizable.css

The /intranet is wrong there again! So somehow something is assembled wrong by TYPO3.

History

#1 Updated by Benni Mack about 1 year ago

  • Target version changed from 8.7.13 to 8.7.19

#2 Updated by Susanne Moog 9 months ago

  • Target version changed from 8.7.19 to Candidate for patchlevel

#3 Updated by Benni Mack 2 months ago

  • Category changed from Miscellaneous to System/Bootstrap/Configuration

Also available in: Atom PDF