Issue Bug Closed

#45834Detection of curlProxyServer settings buggy on upgrade to 6.0

Ernesto Baschny 02/25/13, 19:24 updated 10/02/18, 12:15

Description

In #28344 “HTTP Request2” API was included. It supports detecting old school “curlProxyServer” settings and transfer these to the “new” setting under HTTP:

    $proxyParts = explode(':', $GLOBALS['TYPO3_CONF_VARS']['SYS']['curlProxyServer'], 2);
    $GLOBALS['TYPO3_CONF_VARS']['HTTP']['proxy_host'] = $proxyParts[0];
    $GLOBALS['TYPO3_CONF_VARS']['HTTP']['proxy_port'] = $proxyParts[1];

This code ended up in Core/Bootstrap::transferDeprecatedCurlSettings() after namespace and bootstrapification.

I have always set up this setting like this:

$GLOBALS['TYPO3_CONF_VARS']['SYS']['curlProxyServer'] = 'http://proxy:3128';

I guess the implementator of the transferDeprecatedCurlSettings was only thinking about the “proxy:3128” kind of syntax. I end up with:

$GLOBALS['TYPO3_CONF_VARS']['HTTP']['proxy_host'] = 'http'
$GLOBALS['TYPO3_CONF_VARS']['HTTP']['proxy_port'] = '//proxy:3128;

Other than that, I would also auto-set [‘HTTP’][‘adapter’] to ‘curl’ if legacy ‘curlUse’ = TRUE.

Reviews 7