Re: com web/php: Let the client decide which protocol to use rather than defining it statically in the code (except where applicable).:
include/layout.inc styles/phpnet.css

Interesting, I had no idea that would work with //different.domain.com/path as that just looks horribly wrong. But how will that affect https://php.net/strpos vs http://php.net/strpos results now? Will it be indexed 2 times and become two different results on search engines? since we now advertise two different canonical urls... -Hannes On Mon, Dec 3, 2012 at 9:12 AM, Daniel Brown <danbrown@php.net> wrote: > On Mon, Dec 3, 2012 at 12:11 PM, Hannes Magnusson > <hannes.magnusson@gmail.com> wrote: >> >> Is // some new trick I am unaware of and my browser doesn't understand? >> >> >> All these links look very broken to me. > > No, it's been around for years. Using // as opposed to > http:// or > https:// causes the client to dynamically perform the request > using > the same protocol of the parent page. > > -- > </Daniel P. Brown> > Network Infrastructure Manager > http://www.php.net/