CURLOPT_SSL_VERIFYHOST - this option just sounds like "should I verify
host?", when it must sound like "what verifying strategy should I use?"
On Thu, 25 Oct 2012 10:19:24 +0400, Adam Harvey wrote:
On 25 October 2012 13:46, JJ wrote:
On Wed, Oct 24, 2012 at 10:34 PM, Sherif Ramadan
wrote:
On Wed, Oct 24, 2012 at 11:21 PM, Sherif Ramadan wrote:
> On Thu, Oct 25, 2012 at 1:46 AM, JJ wrote:
> > On Wed, Oct 24, 2012 at 10:34 PM, Sherif Ramadan
> > wrote:
> >> I understand there are people out there that don't read the
> >> documentation and aren't aware of the difference between
> >>
On Thu, Oct 25, 2012 at 1:46 AM, JJ wrote:
> On Wed, Oct 24, 2012 at 10:34 PM, Sherif Ramadan
> wrote:
>> I understand there are people out there that don't read the
>> documentation and aren't aware of the difference between
>> curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 2); and curl_setopt($ch,
>>
On 25 October 2012 13:46, JJ wrote:
> On Wed, Oct 24, 2012 at 10:34 PM, Sherif Ramadan
> wrote:
>> I understand there are people out there that don't read the
>> documentation and aren't aware of the difference between
>> curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 2); and curl_setopt($ch,
>> CURLOP
On Wed, Oct 24, 2012 at 10:34 PM, Sherif Ramadan
wrote:
> I understand there are people out there that don't read the
> documentation and aren't aware of the difference between
> curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 2); and curl_setopt($ch,
> CURLOPT_SSL_VERIFYHOST, true); but still... I don't
On Thu, Oct 25, 2012 at 1:03 AM, JJ wrote:
> Hey all - I'd like start a discussion around pull request 221
> (https://github.com/php/php-src/pull/221).
>
> In short, there's a high volume of [incorrect] code out there which looks
> like:
>
> curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, true);
>
> Ins
Hey all - I'd like start a discussion around pull request 221
(https://github.com/php/php-src/pull/221).
In short, there's a high volume of [incorrect] code out there which looks like:
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, true);
Instead of what, in all likelyhood, the code meant to do:
curl
> From: Anthony Ferrara [mailto:ircmax...@gmail.com]
>
> > [Pierre said:]
> > It is still the case.
> >
> > I for one would like to kill all the legacy features or too specific
> > features which are really unusable by any common developers.
> >
> > Other developers may disagree but it makes very h
