31–40 of 361 posts
Perhaps this something that a browser should be doing, instead of websites themselves?
Standalone program on Windows XP (or maybe Windows 98?). It had it's own window where you could see which pages it was loading.
Does anyone know the name?
Embedding via // without explicit SSL should probably be considered harmful or malicious as there is no reason to make such scripts available without SSL. Even if the end website is not using SSL users can still fetch your script securely.
Embedding via // without explicit SSL should probably be considered harmful or malicious as there is no reason to make such scripts available without SSL. Even if the end website is not using SSL users can still fetch your script securely.
[1] https://developer.mozilla.org/en-US/docs/Web/Security/Subres...
Embedding via // without explicit SSL should probably be considered harmful or malicious as there is no reason to make such scripts available without SSL. Even if the end website is not using SSL users can still fetch your script securely.
There’s no security gain from going to HTTPS if the site is served over HTTP, but there’s a small speed hit.
Separately to that, the communication between the user and your server when downloading your script is secured by your SSL. This can be secure even if example.com is not, so it should only be secure.
Embedding via // without explicit SSL should probably be considered harmful or malicious as there is no reason to make such scripts available without SSL. Even if the end website is not using SSL users can still fetch your script securely.
There’s no security gain from going to HTTPS if the site is served over HTTP, but there’s a small speed hit.
I’m wondering if a possible use case for this is to use it to warm up app servers when doing deployments? Enumerate through a list of pages on your site and use something like Puppeteer to simulate hovering over links on each page.
This sounds like a computer processor's branch prediction algorithm.
Earlier quoted context omitted.
There’s no security gain from going to HTTPS if the site is served over HTTP, but there’s a small speed hit.
No site should be served over plain HTTP in 2019. Browsers and search engines are actively discouraging/downranking websites that don't use TLS at this point.
Perhaps this something that a browser should be doing, instead of websites themselves?
I remember using some web accelerator 15-20 years ago. Prefetching all links on webpages. It was really helpful on modem/ISDN connection. Standalone program on Windows XP (or maybe Windows 98?). It had it's own window where you could see which pages it was loading. Does anyone know the name?