3 ms·
Why not just use https:// https:// ? That way, if you load the file using file:// it will still work. Any downsides?
by jonny_eh 14y ago
Why not just use https:// https:// ?
That way, if you load the file using file:// it will still work. Any downsides?
- jonknee 14y agoYou will often need to dynamically generate all URLs depending on the current state of the page. A common example is an econmerce site where normal pages are HTTP, but things like the shopping cart and checkout are HTTPS. Your template will need to know to load resources as HTTPS when on a secure page. It's not the end of the world, but certainly annoying.