Bug #14410
closedRealURL does not work, because TYPO3_SITE_URL value is wrong
Added by old_pneff almost 20 years ago. Updated almost 12 years ago.
0%
Description
I'm trying to get RealURL 0.2.0 working on a TYPO3 3.7.0 installation. Generating the links always worked fine, but whatever URL I browsed to, it always showed the main page.
So http://mysite/1/ showed the same page as for example http://mysite/5/ - the one you see when going on http://mysite/index.php directly.
Debugging the problem I found, that the function t3lib_div::getIndpEnv seems to return a wrong value for TYPO3_SITE_URL. It always returned the full URL I entered into the browser. So for the examples above it returned http://mysite/1/ and http//mysite/5/.
When I changed the function to return "http://mysite/" (hardcoded) it worked.
Is this indeed a bug or am I just too stupid to live on this planet and use TYPO3?
(issue imported from #M541)
Updated by Peter Niederlag almost 20 years ago
seems like some misconfiguration to me. hard to tell without any specific details...
Updated by old_bpusch2 almost 20 years ago
I had the same problems.
Here the results of t3lib_getIndpEnv('_ARRAY'):
[HTTP_HOST] => test.test
[TYPO3_HOST_ONLY] => test.test
[TYPO3_PORT] =>
[PATH_INFO] =>
[QUERY_STRING] =>
[REQUEST_URI] => /unternehmen/impressum.html
[HTTP_REFERER] =>
[TYPO3_REQUEST_HOST] => http://test.test
[TYPO3_REQUEST_URL] => http://test.test/unternehmen/impressum.html
[TYPO3_REQUEST_SCRIPT] => http://test.test/unternehmen/impressum.html
[TYPO3_REQUEST_DIR] => http://test.test/unternehmen/
[TYPO3_SITE_URL] => http://test.test/unternehmen/
[TYPO3_SITE_SCRIPT] => impressum.html
[TYPO3_SSL] =>
[SCRIPT_NAME] => /unternehmen/impressum.html
[TYPO3_DOCUMENT_ROOT] =>
[SCRIPT_FILENAME] => C:/www/dummy-3.7.0/index.php
[REMOTE_ADDR] => 127.0.0.1
[REMOTE_HOST] =>
[HTTP_USER_AGENT] => Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5) Gecko/20041108 Firefox/1.0
[HTTP_ACCEPT_LANGUAGE] => de-de,de;q=0.8,en-us;q=0.5,en;q=0.3
TYPO3_SITE_URL always returns the whole path up to the last slash.
But 'unternehmen' should be part of TYPO3_SITE_SCRIPT, as it is not part of the path to the typo3 frontend but the name of a first level page.
As realurl uses all levels to generate (encode) the path, it should be given the whole path for decoding. Using the 'impressum.html' only, realurl fails to decode the path.
As I am hosting more than one domain within a single installation, I used a dirty quickfix: I made tslib_fe::checkAlternativeIdMethods() use SCRIPT_NAME (and actually strip the leading slash as this makes realurl search for a page named '', as the path is exploded by slashes).
I didn't want to mess up too much in the code as I'm quite new to typo3 and still trying to get my bearings..
So there might be two approaches to changing this behaviour:
1.
Change calculations inside of getIndpEnv to only return the part of the path which is really useful to realurl . But as far as I can see, this would only work if typo3 was called without using aliases, as one cannot tell by the informations held in the $_SERVER variable, which part of the URL was used to find the typo3 directory and which part is simulated by realurl.
2.
Always return the whole path and let realurl do the work. If I am getting it right, x_realurl_advanced::searchTitle() (used if no cached path is found) searches from the beginning of the path. So if the path was 'path/to/installation/level1/level2.html' it would give up after 'path', as a page with this name/alias/etc. does not exist.
Only using level2.html (as it is now) does only work one level deep, because realurl checks for the pid of the page, which in level2 is the uid of the 'level1' page (and not the uid of the root page which realurl expects it to be).
So it should be searching from the back of the path til reaching the wanted pid - or not reaching it, if the path does not exist.
So, I hope I did get everything right and have been able to explain the problem and possible solutions quite clearly.
Oh, here's the corresponding realurl configuration:
$TYPO3_CONF_VARS['EXTCONF']['realurl']['test.test']['fileName']['defaultToHTMLsuffixOnPrev'] = 1;
$TYPO3_CONF_VARS['EXTCONF']['realurl']['test.local.test']['pagePath'] = array('type'=>'user',
'userFunc'=>'EXT:realurl/class.tx_realurl_advanced.php:&tx_realurl_advanced->main',
'rootpage_id' => 47);
Updated by old_GK_Over almost 20 years ago
I also have the same problem:
I have three websites at one Typo3-Installation.
E.g. http://www.in-memoriam-gabi.de is working well, but http://www.bellowski.de has the same problem like described above.
I spent many weeks without beeing able to solve the problem. :-(
edited on: 04.02.05 01:31
Updated by Karsten Dambekalns over 19 years ago
I can confirm the problem, and the statement about TYPO3_SITE_URL being wrong. What is greek to me, is the cause of this. I have talked to people having realURL working fine, where the value is correct. This has been reported for PHP 4 and 5, so it doesn't seem to be a PHP issue, and Apache 1.3.x is used for working and non-working sites.
The major point seems to be finding out what causes this. So, please add your setup. Here's mine:
TYPO3 3.8.0
realURL 0.3.0
Apache 1.3.33
PHP 4.3.10
Installed in the document root
regular and simulateStatic URLS working fine
Updated by old_babel over 19 years ago
Look at bug #0001274. I think the two are related.
Updated by Stefan B¼hler over 19 years ago
---------
[...]
- If you use the RealUrl extension, then you'll have to enable the next line.
- You will have to change this path if your TYPO3 installation is located
- in a subdirectory of the website root. #
- If you place this in httpd.conf, you cannot use this directive in any case!
RewriteBase /
[...]
--------------
The following httpd.conf works for me:
--------------
RewriteRule ^/(typo3|typo3temp|typo3conf|t3lib|tslib|fileadmin|uploads|showpic\.php)(/.*)?$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-l
RewriteRule ^/(.*)$ /index.php [L,E=ORIG_SCRIPT_NAME:/index.php]
--------------
See the related bug.
Updated by Bj¶rn Kraus about 19 years ago
Perhaps this can solve the issue on IIS installations:
The problem why Typo3 can't return the correct page is that IIS doesn't have the 'REQUEST_URI' variable in $_SERVER. The synonym for this seems to be 'HTTP_SCRIPT_URL'. So I decided to add four lines in the 'getIndpEnv' function (class.t3lib_div.php):
case 'REQUEST_URI':
if (!$_SERVER['REQUEST_URI']) {
--> if (isset($_SERVER['HTTP_SCRIPT_URL'])) {
--> return $_SERVER['HTTP_SCRIPT_URL'];
--> } else {
return '/'.ereg_replace('^/','',t3lib_div::getIndpEnv('SCRIPT_NAME')).
($_SERVER['QUERY_STRING']?'?'.$_SERVER['QUERY_STRING']:'');
--> }
} else return $_SERVER['REQUEST_URI'];
break;
Hope that helps.
Regards
Bjoern
Updated by Hans-Peter Oeri almost 18 years ago
Sorry, if I'm wrong, but I'm rather new to typo3 - and ran into the problem described here...
Isn't the algo for TYPO3_SITE_URL just wrong? It looks from the end - rather than from the beginning of the URL. I suggest:
--- pseudo diff ---
case 'TYPO3_SITE_URL':
if (defined('PATH_thisScript') && defined('PATH_site')) {
$lPath = substr(dirname(PATH_thisScript),strlen(PATH_site));
$retVal = t3lib_div::getIndpEnv('TYPO3_REQUEST_HOST') . '/' . $lPath . ($lPath > '' ? '/' : '');
}
break;
--- pseudo diff ---
... which works like a charm for me ;)
Please enlighten me.
HPO
Updated by Peter Niederlag over 14 years ago
Is this still a problem? In which menu/function/extension does this bug show up? Can it be reproduced somehow? Big Thx for any further hints, otherwise I'll proceed and close it again ...
Updated by Anonymous over 14 years ago
Yes, it is still valid. For example, I am sometimes using Stefan Bühler's work-around, but it is still not making the issue solved.
Updated by Peter Niederlag over 14 years ago
- Version of TYPO3?
- realurl enabled? which Version?
- mod_php or php as cgi?
- windows/mac/linux?
"Doesn't work" is really hard to fix ....
Updated by Helmut Hummel about 13 years ago
- Status changed from Accepted to Needs Feedback
- Target version deleted (
0)
Updated by Jigal van Hemert almost 12 years ago
- Status changed from Needs Feedback to Closed
Open for too long without feedback. Considering the large number of installations with working RealURL / cooluri / etc. url rewriters this doesn't seem to be a problem anymore.