Bug #15697
closedHTTP Proxy Support missing
0%
Description
The SOAP-Clients are created without passing the proxy parameters which are used by the Core's HTTP-functions. Therefore the Ext.-Manager does not work behind a (mandatory) proxy.
I added a quick fix to typo3/mod/tools/em/class.em_soap.php which should work for nusoap and pearsoap, for phpsoap I did not find any documentation.
(issue imported from #M2663)
Files
Updated by Karsten Dambekalns almost 18 years ago
I did not implement this because it would have needed stream context support at some point, which was not available in our supported PHP versions... This can probably go into 4.1, as we will raise the PHP version dependency to 4.3 as it seems. I'll check.
Updated by HO Thi almost 18 years ago
PHP 5.1.2
Typo3 4.0.4
I've tried to upload an extension to the TER with the file class.em_soap.php attached here.
It seems to do a step further than before, but I get the following message : SOAP-ENV:Client: Bad Request.
Can someone give a definitive fix? Thanks a lot.
Updated by Karsten Dambekalns almost 16 years ago
As far as I know nothing has been done towards that end, definitely not by me. Feel free to grab the issue! ;)
Updated by Thomas Trethan over 13 years ago
in Typo3 4.5.2 in typo3/sysext/em/classes/connection/class.tx_em_connection_soap.php before line 89 where SoapClient is instantiated:
if ($proxyServer = parse_url($GLOBALS['TYPO3_CONF_VARS']['SYS']['curlProxyServer'])) {
if ($proxyServer['host']) {
$options['soapoptions']['proxy_host'] = $proxyServer['host'];
}
if ($proxyServer['port']) {
$options['soapoptions']['proxy_port'] = $proxyServer['port'];
}
if ($proxyCreds = explode(':', $GLOBALS['TYPO3_CONF_VARS']['SYS']['curlProxyUserPass'])) {
$options['soapoptions']['proxy_login'] = $proxyCreds[0];
$options['soapoptions']['proxy_password'] = $proxyCreds[1];
}
}
Updated by Helmut Hummel about 13 years ago
- Status changed from New to Needs Feedback
- Target version deleted (
0) - PHP Version deleted (
4)
This is fixed in 4.5 right?
Updated by Martin Muskulus about 13 years ago
In TYPO3 v4.6.0 proxy support works for
- downloading mirror list
- downloading language files
- importing extensions from ter
BUT it doesn't work not for downloading My Extension's list
I add my typo3.org account credentials in the settings tab to activate my extensions tab. Opening my extensions tab causes timeout while fetching my extensions list.
typo3's syslog says:
Core: Error handler (BE): PHP Warning: SoapClient::__doRequest(): connect() failed: Connection timed out in /opt/typo3_src-4.6.0/typo3/sysext/em/classes/connection/class.tx_em_connection_soap.php line 214
Adding Thomas code to typo3/sysext/em/classes/connection/class.tx_em_connection_soap.php solves the problem for me.
Updated by Alexander Opitz over 11 years ago
- TYPO3 Version changed from 4.0 to 4.6
As 4.6 isn't supported anymore, does this problem exists in 4.7?
Anyway, in the next months there may be an extension uploder on the t3o page and the upload feature from the EM will be removed. So if not fixed it may be closed anyway as won't fixed.
Updated by Martin Muskulus over 11 years ago
The problem still exists in 4.7.10.
from apaches log:
PHP Fatal error: SOAP-ERROR: Parsing WSDL: Couldn't load from 'http://typo3.org/wsdl/tx_ter_wsdl.php' : failed to load external entity "http://typo3.org/wsdl/tx_ter_wsdl.php"\n in /opt/typo3_src-4.7.10/typo3/sysext/em/classes/connection/class.tx_em_connection_soap.php on line 88
I applied the same fix. But filtering my extension list by name will flash an error message in the typo3 backend
invalid
internal server error
Using Opera Dragonfly I can see this is the result of the HTTP/1.1 POST to /typo3/ajax.php?ajaxID=ExtDirect::route&namespace=TYPO3.EMSOAP but i'm not into typo3 ajax to debug any further.
Updated by Alexander Opitz over 11 years ago
- Assignee set to Alexander Opitz
- TYPO3 Version changed from 4.6 to 4.7
Updated by Alexander Opitz over 11 years ago
- Status changed from Needs Feedback to Accepted
Updated by Wouter Wolters almost 10 years ago
- Status changed from Accepted to Closed
- Is Regression set to No
Extension upload functionality has been removed from TER. Use other upload tools, or upload directly using the interface on typo3.org
Updated by Wouter Wolters almost 10 years ago
- Status changed from Closed to Accepted
This is also about getting extensions. Reopened again.
Updated by Helmut Hummel almost 10 years ago
- Status changed from Accepted to Closed
No Soap calls in 6.x any more to fetch the extension list