4 ms·
It's to do with the browser security model and JavaScript restrictions on file:// paths. I'm not entirely sure of the class of attack that it prevents, but it'
by shitloadofbooks 11y ago
It's to do with the browser security model and JavaScript restrictions on file:// paths.
I'm not entirely sure of the class of attack that it prevents, but it's been that way for quite a while now.
- scott_karana 11y agoFor a while, browsers allowed unfettered Javascript access to local files, so malware sites would just get users to save the site, and run it. Tada, access to local files, or unlimited XHR requests for DDoSing, etc. :-)