[PHP-DEV] Re: Internationalized Domain Name support in FILTER_VALIDATE_URL

On Fri, Sep 19, 2014 at 1:24 PM, Kévin Dunglas wrote: > Hi, > > The flag is a good idea to handle old systems but the feature must be > enabled by default (at least for PHP 7) and disablable through the flag. > IDN RFCs are more than 10 years old. All major browsers and registrars > support IDN.

[PHP-DEV] Re: Internationalized Domain Name support in FILTER_VALIDATE_URL

Hi, The flag is a good idea to handle old systems but the feature must be enabled by default (at least for PHP 7) and disablable through the flag. IDN RFCs are more than 10 years old. All major browsers and registrars support IDN. Le vendredi 19 septembre 2014, Tjerk Meesters a écrit : > > On 1

[PHP-DEV] PHP 5.4.33 Released

Hello! The PHP development team announces the immediate availability of PHP 5.4.33. 10 bugs were fixed in this release. All PHP 5.4 users are encouraged to upgrade to this version. This release is the last planned release that contains regular bugfixes. All the consequent releases will contain on

Re: [PHP-DEV] Internationalized Domain Name support in FILTER_VALIDATE_URL

On 19 Sep 2014, at 06:52, Andrea Faulds wrote: > > On 18 Sep 2014, at 21:26, Kévin Dunglas wrote: > >> I'm working on enhancing the FILTER_VALIDATE_URL filter ( >> https://github.com/php/php-src/pull/826). >> The current implementation does not support validation of internationalized >> domai

Re: [PHP-DEV] Internationalized Domain Name support in FILTER_VALIDATE_URL

On 18 Sep 2014, at 21:26, Kévin Dunglas wrote: > I'm working on enhancing the FILTER_VALIDATE_URL filter ( > https://github.com/php/php-src/pull/826). > The current implementation does not support validation of internationalized > domain names (i.e: http://www.académie-française.fr/ >

Re: [PHP-DEV] Why does checkdnsrr() default to MX??

On 18 September 2014 22:47:36 GMT+01:00, Sanford Whiteman wrote: >I was just composing an e-mail advising you to follow general >netiquette >rules and read the original post. :) Yeah, for some reason your first message shows up as a standalone post, with no hint that it was a reply, so I comple

[PHP-DEV] Re: [PHP-CVS] com php-src: fix CG(empty_string) init in ZTS: Zend/zend.c

Hi Nikita, On Thu, September 18, 2014 22:34, Nikita Popov wrote: > On Thu, Sep 18, 2014 at 5:14 PM, Anatol Belski wrote: > > >> Commit:e8b497ad8eb74273f7f44ae7e515e7a5e95b50f7 >> Author:Anatol Belski Thu, 18 Sep 2014 16:45:50 >> +0200 >> Parents: f162b3f736f07ad868abec6ea8b44a9

Re: [PHP-DEV] Why does checkdnsrr() default to MX??

... thought I just top-posted for the first time in, like, ever -- b/c I guess janky Gmail does that by default (I had to switch my subscribed address as php.net was deleting mail relayed through my ISP).

Re: [PHP-DEV] Why does checkdnsrr() default to MX??

I was just composing an e-mail advising you to follow general netiquette rules and read the original post. :) I disagree utterly that I did not sufficiently address the question. I addressed it in multiple ways: [1] ANY queries create extraneous traffic, so you want fewer PHP functions defaulting

Re: [PHP-DEV] Why does checkdnsrr() default to MX??

On 18 September 2014 22:19:46 GMT+01:00, Rowan Collins wrote: > >I hope this message doesn't sound too negative, and look forward to >clarification of your thoughts. > > Apologies, I've just realised that that message wasn't in fact the beginning of the thread, so some of my comments are way o

Re: [PHP-DEV] Why does checkdnsrr() default to MX??

On 18 September 2014 21:31:33 GMT+01:00, Sanford Whiteman wrote: >ANY (*) requests are key to many DNS amplification attacks and may >fail, >even if the RR you want exists when individually requested. Such >requests >should be discouraged by clients, IMO. It's disappointing that PHP's >dns_get_re

[PHP-DEV] Why does checkdnsrr() default to MX??

ANY (*) requests are key to many DNS amplification attacks and may fail, even if the RR you want exists when individually requested. Such requests should be discouraged by clients, IMO. It's disappointing that PHP's dns_get_record() defaults to ANY. But more to the point, what is the client-side u

[PHP-DEV] Internationalized Domain Name support in FILTER_VALIDATE_URL

Hello, I'm working on enhancing the FILTER_VALIDATE_URL filter ( https://github.com/php/php-src/pull/826). The current implementation does not support validation of internationalized domain names (i.e: http://www.académie-française.fr/ ). Support of IDN

[PHP-DEV] Why does checkdnsrr() default to MX??

Hey guys, I just spent some time troubleshooting what appeared to be a DNS issue before I realized that, absent the optional $type argument, checkdnsrr() defaults to "MX". Can anybody explain why it's defaulting to "MX" and not "ANY"? It seems really counter-intuitive. --Kris

Re: [PHP-DEV] RFC: Removal of dead SAPIs

Hi Marius, On Thu, September 18, 2014 11:08, marius adrian popa wrote: > Maybe is time to vote and implement it in php 7 with a pull request for > each sapi > > https://wiki.php.net/rfc/removal_of_dead_sapis > > > tux is dead for almost 10 years > > thttpd does have a fork that seems maintained fr

Re: [PHP-DEV] [RFC] Implicit isset() in Shorthand Ternary Operator

>On Sep 18, 2014 9:36 AM, "Johannes Schlüter" wrote: > > On Thu, 2014-09-18 at 12:41 +0100, Andrea Faulds wrote: > > We could use a function *syntax*, though, but I don’t like this idea. > > coalesce() and ifsetor() are both ugly to me, and it’s not super > > obvious what they do: > > > > var_

Re: [PHP-DEV] [RFC] Implicit isset() in Shorthand Ternary Operator

On 18 September 2014 14:34, Johannes Schlüter wrote: > On Thu, 2014-09-18 at 12:41 +0100, Andrea Faulds wrote: >> We could use a function *syntax*, though, but I don’t like this idea. >> coalesce() and ifsetor() are both ugly to me, and it’s not super >> obvious what they do: >> >> var_dump(co

Re: [PHP-DEV] [RFC] Implicit isset() in Shorthand Ternary Operator

On Thu, 2014-09-18 at 12:41 +0100, Andrea Faulds wrote: > We could use a function *syntax*, though, but I don’t like this idea. > coalesce() and ifsetor() are both ugly to me, and it’s not super > obvious what they do: > > var_dump(coalesce($_GET[‘foobar’], 3)); > > vs. > > var_dump($_GE

[PHP-DEV] Re: PHP 5.5.17RC1 is ready for testing

What's the benefit of doing a Release Candidate/QA cycle when fixes for regressions aren't merged to the final release? See https://bugs.php.net/bug.php?id=67965 Regression reported and fixed, but fix not merged to 5.5.17 branch. Commit https://github.com/php/php-src/commit/f86b2193a483f56b0bd

Re: [PHP-DEV] [RFC] Implicit isset() in Shorthand Ternary Operator

Pete Boere wrote (on 18/09/2014): I'm seeing '??' as analogous to the way JS developers use '||', and I use that all the time when writing JS. Actually, JS's || is more analogous to the existing ?: operator, because it checks for truthiness, not definedness (!empty() rather than isset(), in P

Re: [PHP-DEV] [RFC] Implicit isset() in Shorthand Ternary Operator

On 18 Sep 2014, at 12:32, Pete Boere wrote: > I'm seeing '??' as analogous to the way JS developers use '||', and I use > that all the time when writing JS. PHP already has a direct equivalent to ||, namely the ?: operator. However, unfortunately PHP always spits out a notice on non-existent i

Re: [PHP-DEV] [RFC] Implicit isset() in Shorthand Ternary Operator

I'm seeing '??' as analogous to the way JS developers use '||', and I use that all the time when writing JS. Personally I wouldn't be interested in a function version because the short-circuiting of '??' is an important distinction; not something you can replicate with a function. Therefore having

Re: [PHP-DEV] [RFC] Implicit isset() in Shorthand Ternary Operator

On Sep 17, 2014, at 11:40, Matthew Fonda wrote: > Hi Andrea, > > This is great -- thanks to you and Nikita for the work here. > > Syntax wise, I would prefer a function-like syntax, e.g. coalesce($a, $b, > 'c') or ifsetor() instead of $a ?? $b ?? 'c'. I find this more readable, > and it avoids a

Re: [PHP-DEV] RFC: Removal of dead SAPIs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 18/09/2014 11:08, marius adrian popa a écrit : > Maybe is time to vote and implement it in php 7 with a pull request > for each sapi > > https://wiki.php.net/rfc/removal_of_dead_sapis AFAIK, litespeed is not dead It have be recently updated to lat

[PHP-DEV] RFC: Removal of dead SAPIs

Maybe is time to vote and implement it in php 7 with a pull request for each sapi https://wiki.php.net/rfc/removal_of_dead_sapis tux is dead for almost 10 years thttpd does have a fork that seems maintained from git log http://opensource.dyc.edu/sthttpd http://opensource.dyc.edu/gitweb/?p=sthtt