Re: Re: SSRF protection in curl
| From: | Xavier Leune | Date: | Thu, 29 Oct 2026 14:05:49 +0000 |
| Subject: | Re: Re: SSRF protection in curl | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-132955@lists.php.net to get a copy of this message | ||
Hi Levi,
Good point, with one caveat. I think we might apply the same logic to
streams, but as the decision must be made per-request, the implementation
should be specific per api.
So I'd rather focus on curl here and make sure it lands in 8.7, then we
might open another rfc for streams.
WDYT ?
Le jeu. 22 oct. 2026 à 16:58, Levi Morrison <levi.morrison@datadoghq.com> a
écrit :
> Is there any reason we should intentionally make this curl specific?
> Meaning, we could design support for making it work for streams as
> well, couldn't we? Why make a curl specific feature instead of a
> language wide one?
>