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/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
