Geek Answers Handbook

Does Chrome not follow links to relative protocol urls?

The first time I noticed that Chrome (and only Chrome) does not pay attention to links to the relative URLs of the protocol. For instance:

<img src='//www.example.net/image.png />

should appear as https when it appears on https pages, and should be the http source when it appears on http pages. IE and FF still work this way, but Chrome now only uses it as

 //www.example.net/image.png

therefore, when it appears on an https page, the page becomes insecure. Has anyone else noticed this recently?

+4
source share
1 answer

Chrome respects the relative URL of the protocol, looking at your example, it is incorrect (there is no closure in your path).

+1
source

More articles:


All Articles