TYPO3 Core

The general idea is nice. However, username and password being hardcoded isn't handy at all and this patch won't make it to TYPO3 Core as such.

Hi Thorsten,

I had (and still have) turned into a portal where Apaches' Basic Authentication is activated. My site uses the "mnogosearch" extension (and thus the "pagepath" extension).

I can still reproduce the problem when I change and then save one record in the TYPO3 BE that has to be indexed.

The mnogosearch extension calls (via tx_mnogosearch_tcemain::processDatamap_afterDatabaseOperations) the tx_pagepath_api::getPagePath method. Within this method t3lib_div::getURL will be called. When I debug the code, I notice that the return value of getURL (= curl_exec) is always FALSE:

When I use the "$report" in getURL, I get back this array:

$report : array (
        error: 22,
        message: "The requested URL returned error: 401",
        lib: "CURL)

The two lines I've added (which worked then on a simple HTTP server without proxy) were these:

modified t3lib_div::getURL:
--------------------------
...
curl_setopt($ch, CURLOPT_FAILONERROR, 1);

// Added: Amar --- begin
curl_setopt($ch, CURLOPT_USERPWD, 'curl:'.hash_hmac('md5', 'curl', $GLOBALS['TYPO3_CONF_VARS']['SYS']['encryptionKey']));
curl_setopt($ch, CURLOPT_HTTPAUTH, CURLAUTH_ANY);
// Added: Amar --- end

// May fail (PHP 5.2.0 + and 5.1.5 +) when open_basedir or safe_mode are enabled
$followLocation = @curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1);
...

On the other hand the "Retrieve/Update" in the ExtManager although uses getURL(), but works perfectly... even with a "curlProxyServer".

Anyway my workaround doesn't work for me anymore (in TYPO3 4.4.7). I got to admit that I use SSL and a curl-Proxy now.
But it worked for me at that time with a simple HTTP-Server without a curl-Proxy.

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.1)?