|
|
|
|
|
|
by oni0n56
5698 days ago
|
|
|
Yeah, the reason for that is that
1) if/when we add HTTPS support it will run seamlessly.
For now it just returns a blank file if included over HTTPS, and so the page will degrade gracefully (no tracking) without any security errors that would've come up from loading an http resource.
2) it's shorter. Though you're right it does look a bit weird, I will add a note to the instructions explaining what it is and that its not a bug or anything. Replacing it with http:// would've worked perfectly fine as well. We use the same scheme to link to the media on our CDN so the app can switch seamlessly between http and https secured sections (account,billing) without any different <head> code |
|
|