cURL defaults

[xepozz]

Description

The main problem is cURL doesn't have any default settings and an ability to set them.
So there is no way to control all your outgoing requests. Some reasons to control them globally: proxying, removing some unacceptable headers, encoding, etc.
fopen/file_get_contents/file are great to use shared configuration, but:

• They are not fluent compare to cURL methods
• You cannot control vendor implementations uses cURL

The following code:

<?php
stream_context_set_default([
    'http' => [
        'proxy' => 'http://default-proxy',
    ],
]);
// Works
file_get_contents('https://www.google.com');
// Doesn't work
$ch = curl_init("https://www.google.com/");
curl_exec($ch);

I understand there are two different things, but global settings maybe incredible useful.
Due to cURL doesn't use streams, it would be great to have at least an additional method to set defaults.

So questions:

1. Is there any problems to connect cURL with streams as a stream wrapper?
2. Are there any cons not to share streams context with cURL options?
3. Is it possible to add a method to set defaults?

PHP Version

8.2

Operating System

No response

[KapitanOczywisty]

1. Is there any problems to connect cURL with streams as a stream wrapper?
2. Are there any cons not to share streams context with cURL options?

Besides being hard to map stream context options to corresponding curl ones this would introduce backward compatibility issues.

3. Is it possible to add a method to set defaults?

Such function would be nice, but it has to go through RFC process Also related: https://wiki.php.net/rfc/curl_user_agent

Currently you can keep default options in one handle and clone it instead of calling curl_init:

$defaultCh = curl_init();
curl_setopt($defaultCh, CURLOPT_PROXY, 'http://192.168.0.1:8080');

$ch = clone $defaultCh;
curl_setopt($ch, CURLOPT_URL, 'https://example.com');
curl_exec();

[xepozz]

Currently you can keep default options in one handle and clone it instead of calling curl_init:

Sure, but it won't work for vendor packages.

[blar]

You can set the environment variables http_proxy or HTTPS_PROXY to use a global proxy for all curl requests.

[iluuu1994]

@adoy Your insight would also be helpful here.

[adoy]

I have the same lecture and agree with @KapitanOczywisty. We shouldn't use the stream_context_set_default, curl is not a stream (experimental curl stream context was deleted in PHP 5.5). I think a new curl_* function would be the best. If someone want to write an RFC for it, I can take care of the actual implementation.

[github-actions]

There has not been any recent activity in this feature request. It will automatically be closed in 14 days if no further action is taken. Please see https://github.com/probot/stale#is-closing-stale-issues-really-a-good-idea to understand why we auto-close stale feature requests.

[xepozz]

Up

[github-actions]

There has not been any recent activity in this feature request. It will automatically be closed in 14 days if no further action is taken. Please see https://github.com/probot/stale#is-closing-stale-issues-really-a-good-idea to understand why we auto-close stale feature requests.

[xepozz]

Still want to have

[KapitanOczywisty]

@xepozz There is no point in keeping this issue alive, since you need to follow RFC process to make such changes. Are you willing to do that?

[xepozz]

@KapitanOczywisty yes I'd like to do it, but can't actually try. Give me a few weeks, I'll try to follow the process

[github-actions]

There has not been any recent activity in this feature request. It will automatically be closed in 14 days if no further action is taken. Please see https://github.com/probot/stale#is-closing-stale-issues-really-a-good-idea to understand why we auto-close stale feature requests.