On Thu, Nov 12, 2015 at 7:09 AM, Côme Chilliet wrote:
> Le vendredi 6 novembre 2015, 11:43:58 Ferenc Kovacs a écrit :
> >
> > on the other hand functions like ftp_connect assumes the default port
> when
> > passed NULL:
> >
> > I'm fine with changing this for future versions but my understanding
Le vendredi 6 novembre 2015, 11:43:58 Ferenc Kovacs a écrit :
>
> on the other hand functions like ftp_connect assumes the default port when
> passed NULL:
>
> I'm fine with changing this for future versions but my understanding is
> that this BC break (along with some others) was introduced in a
On Thu, Nov 5, 2015 at 3:41 AM, Bishop Bettini wrote:
> On Tue, Nov 3, 2015 at 11:13 PM, Côme Chilliet wrote:
>
> > I got mail from someone saying that in previous version, calling
> > ldap_connect($host, NULL) would use default port.
> > While now it is considered as trying to use port 0 and tr
Le mercredi 4 novembre 2015, 21:41:20 Bishop Bettini a écrit :
>
> If one wanted truly robust (paranoid) code, you'd probably want to do:
>
> $port = getservbyname('ldap', 'tcp');
>
> if (isset($options['port']) && is_numeric($options['port']))
> $port = intval($options['port']);
>
> $resou
On Tue, Nov 3, 2015 at 11:13 PM, Côme Chilliet wrote:
> I got mail from someone saying that in previous version, calling
> ldap_connect($host, NULL) would use default port.
> While now it is considered as trying to use port 0 and trigger an error.
>
I believe the current behavior (interpret as z
I got mail from someone saying that in previous version, calling
ldap_connect($host, NULL) would use default port.
While now it is considered as trying to use port 0 and trigger an error.
I’m a bit troubled about it because the documentation says:
resource ldap_connect ([ string $hostname = NULL
