Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89056
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <7F.A7.13519.74609365@pb1.pair.com>
To: internals@lists.php.net
References: <3187501.to7rK1FKUl@mcmic-probook>
 <CAEYWF=4too2Uv5fDsB_74VJttDK4J74VhM2Fox_j6nZ-yLnX7A@mail.gmail.com>
 <5638C725.60805@heigl.org>
Date: Tue, 3 Nov 2015 19:07:33 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:41.0)
 Gecko/20100101 Firefox/41.0 SeaMonkey/2.38
MIME-Version: 1.0
In-Reply-To: <5638C725.60805@heigl.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Small regression in PHP-LDAP
From: ajf@ajf.me (Andrea Faulds)

Hi Andreas,

Andreas Heigl wrote:
> +1 on that solution. Just throwing "host:port" onto something doesn't
> help anyone. Try that with "www.google.com:443" in your favourite
> browser. Most will give you an error (if it's not port 80). So those
> people that try it will eventually read the documentation on php.net and
> then see that it's not supported.

If you give the port number for a non-HTTP TCP application then yes, 
your browser will spit an error back at you, because HTTP is the 
implicit URI scheme. That doesn't mean hostname:port is wrong, it's 
perfectly valid for HTTP. Similarly, I could give my LDAP URI as 
google.com:80 and get an error, but I don't think that's a fault with 
hostname:port.

The PHP interpreter itself uses it for HTTP:

$ php -S localhost:8000

I'm unconvinced.

Thanks.
-- 
Andrea Faulds
http://ajf.me/