Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78823 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 67649 invoked from network); 6 Nov 2014 17:57:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Nov 2014 17:57:20 -0000 Authentication-Results: pb1.pair.com smtp.mail=sean@seancoates.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=sean@seancoates.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain seancoates.com from 208.72.237.35 cause and error) X-PHP-List-Original-Sender: sean@seancoates.com X-Host-Fingerprint: 208.72.237.35 pb-smtp1.int.icgroup.com Received: from [208.72.237.35] ([208.72.237.35:55933] helo=sasl.smtp.pobox.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 23/30-65179-E76BB545 for ; Thu, 06 Nov 2014 12:57:19 -0500 Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 942741AFE7; Thu, 6 Nov 2014 12:57:16 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=sasl; bh= 2Iv5wQDYWaynb3A+cLhU3CZYJ4E=; b=BFHDwuLJQyvEqd4GpYr2vccs+EmjlE0r xu7/SjJpmD3iAhERlkAxbPexkZ8wyudFyuvh5MF4Ec9CZLn45J6Z6RYjuZxNPBKY lsrwkhk900IseVZ7vNWF2IjfoLe+TrWuc0qgSFxnmkbSrH15EsbLg5H/0BFBkb+l TPIdQXp97NQ= Received: from pb-smtp1.int.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 8A7C21AFE5; Thu, 6 Nov 2014 12:57:16 -0500 (EST) Received: from [192.168.0.18] (unknown [99.231.128.63]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 895451AFA0; Thu, 6 Nov 2014 12:56:14 -0500 (EST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) In-Reply-To: Date: Thu, 6 Nov 2014 12:56:14 -0500 Cc: =?utf-8?Q?K=C3=A9vin_Dunglas?= , Daniel Ribeiro , PHP Internals Content-Transfer-Encoding: quoted-printable Message-ID: References: To: Andrey Andreev X-Mailer: Apple Mail (2.1990.1) X-Pobox-Relay-ID: 335F8F86-65DE-11E4-9392-42529F42C9D4-96568589!pb-smtp1.pobox.com Subject: Re: [PHP-DEV] Better RFC conformance for FILTER_VALIDATE_URL From: sean@seancoates.com (Sean Coates) > On Thu, Nov 6, 2014 at 3:39 PM, K=C3=A9vin Dunglas = wrote: >> FILTER_VALIDATE_DOMAIN checks conformance with DNS RFCs : total = length, >> label length and allowed characters (_ are allowed in domain names = but many >> other characters are forbidden such as ~/+...). I'll add IDN support = too >> when IDN support for streams will be merged. >=20 > I am not trying to argue, but where does it say that ~/+ are > disallowed, yet an underscore is? The only rule *allowing* underscores > that I've seen is the one that says any binary string is a valid DNS > record value. FWIW, there *is* a practical in-use (de facto if nothing else) = convention of using _ in hosts for DKIM: $ dig +short -ttxt mandrill._domainkey.mailchimp.com "k=3Drsa\; = p=3DMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hM= B3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3= tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB\;= =E2=80=9D S=