Feature #31818
closed
Implement curl proxy blacklist in t3lib_div::getUrl
Added by Michel Nederlof about 13 years ago.
Updated over 9 years ago.
Description
In our network we have a proxy server which allows outbound traffic, but in case of internal network access, the proxy server is not able to connect.
Since we all should use t3lib_div::getURL to get resources, I implemented a proxy blacklist when curl is used.
In the localconf.php you can add a line like this:
$TYPO3_CONF_VARS['SYS']['curlProxyBlackList'] = '*.example.com, www.google.com';
Now any subdomain of example.com and the host www.google.com will not be fetched via the proxy.
See the attached unified diff how i've implemented it.
It would be great if this could be integrated into TYPO3.
Files
- Status changed from New to Accepted
- Priority changed from Should have to Could have
- Target version changed from 4.5.8 to 4.7.0
- % Done changed from 90 to 0
- Complexity changed from easy to medium
Problem here is that it is a new feature, which can only go into a new version. On top of that there is a new http library introduced (see t3lib_http_request).
This could be an extra feature when t3lib_div::getUrl gets rewritten to use the http library.
I don't think it should be called a "black list". Black list is something you want to forbid or avoid because it is bad. I would prefer the other name, something like "proxyBypassDomains".
- Assignee set to Tolleiv Nietsch
Seems like something which should be put in before feature freeze - would you mind to push it to Gerrit? Besides that I agree with Dmitry - it's not a blacklist but a bypass-option. Anyways - needs to get to Gerrit before feature freeze.
- Target version deleted (
4.7.0)
- Target version set to 7.4 (Backend)
- Target version changed from 7.4 (Backend) to 7.5
Feature will be handled by the main ticket #28258 where all cURL option tickets are consolidated.
- Status changed from Accepted to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by