#26088Pagetree of 4.5.2 backend is not loaded via Proxy
Description
For security reasons, some of our TYPO3-backends are only accessible via a proxy. Let`s assume that the name of the proxy is “proxy.server2.de” and that it points to a webserver called “direct.server2.de”. If I call a TYPO3 4.5.2 backend via proxy, I get the following error:
Connection Problem Sorry, but an error occurred while connecting to the server. Please check your network connection.
If I look at the http headers in Firefox while loading the BE via Proxy:
00:00:23.630 0.928 717 (1377) GET 304 application/javascript http://proxy.server2.de/typo3temp/compressor/flashmessages-b0c0fac69ab73fd0631227ec3ccbfaf4.js?1303115435 00:00:40.573 0.151 595 381 OPTIONS 303 text/html (NS_ERROR_DOM_BAD_URI) http://direct.server2.de/typo3/ajax.php?ajaxID=ExtDirect::route&namespace=TYPO3.Components.PageTree 00:00:40.897 0.642 595 381 OPTIONS 303 text/html (NS_ERROR_DOM_BAD_URI) http://direct.server2.de/typo3/ajax.php?ajaxID=ExtDirect::route&namespace=TYPO3.Components.PageTree 00:00:23.734 0.866 598 381 OPTIONS 303 text/html (NS_ERROR_DOM_BAD_URI) http://direct.server2.de/typo3/ajax.php?ajaxID=ExtDirect::route&namespace=TYPO3.ExtDirectStateProvider
I can see that /ajax.php is referenced with the name of the webserver. I suppose that the name of the webserver is obtained via TYPO3_SITE_URL or some other global variable.
If this is the case, could you please implement an optional way of setting the server name those components are loaded from? Maybe config.baseURL or a conf-var from the localconfig.php.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.