Project

General

Profile

Actions

Feature #31818

closed

Implement curl proxy blacklist in t3lib_div::getUrl

Added by Michel Nederlof over 12 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Could have
Category:
-
Target version:
Start date:
2011-11-15
Due date:
% Done:

0%

Estimated time:
PHP Version:
5.3
Tags:
Complexity:
medium
Sprint Focus:

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

class.t3lib_div.php.diff (2.37 KB) class.t3lib_div.php.diff Michel Nederlof, 2011-11-15 14:21

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #28258: cURL: allow custom curl paramsRejected2011-07-16

Actions
Has duplicate TYPO3 Core - Feature #27669: Proxy Exceptions for CurlClosed2011-07-102011-07-10

Actions
Actions #1

Updated by Jigal van Hemert over 12 years ago

  • 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.

Actions #2

Updated by Dmitry Dulepov over 12 years ago

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".

Actions #3

Updated by Tolleiv Nietsch about 12 years ago

  • 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.

Actions #4

Updated by Steffen Ritter about 12 years ago

  • Target version deleted (4.7.0)
Actions #5

Updated by Mathias Schreiber over 9 years ago

  • Target version set to 7.4 (Backend)
Actions #6

Updated by Susanne Moog over 8 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions #7

Updated by Susanne Moog over 8 years ago

Feature will be handled by the main ticket #28258 where all cURL option tickets are consolidated.

Actions #8

Updated by Susanne Moog over 8 years ago

  • Status changed from Accepted to Closed
Actions

Also available in: Atom PDF