Firefox Will Block Navigational Data URIs as Part of an Anti-Phishing Feature (bleepingcomputer.com)
Catalin Cimpanu, writing for BleepingComputer: Mozilla will soon block the loading of data URIs in the Firefox navigation bar as part of a crackdown on phishing sites that abuse this protocol. The data: URI scheme (RFC 2397) was deployed in 1998 when developers were looking for ways to embed files in other files. What they came up with was the data: URI scheme that allows a developer to load a file represented as an ASCII-encoded octet stream inside another document. Since then, the URI scheme has become very popular with website developers as it allows them to embed text-based (CSS or JS) files or image (PNG, JPEG) files inside HTML documents instead of loading each resource via a separate HTTP request. This practice became hugely popular because search engines started ranking websites based on their page loading speed and the more HTTP requests a website made, the slower it loaded, and the more it affected a site's SERP position.
Why do they always need to re-invent the wheel? Why can't they use RFC 3514 like everybody else?
#DeleteFacebook
So...they are blocking embedded files now?
Web sites like CNN are excruciatingly slow because they are selling your ad space off in real time to a dozen different agencies.
(-1: Post disagrees with my already-settled worldview) is not a valid mod option.
And why is there so much Mozilla spam on here lately? This is not MMN: the Mozilla News Network.
I believe slashdot uses that to embed ads so they can't be blocked. If you view page source on the main slashdot page you'll see what I mean. Of course I could be misunderstanding what Mozilla is saying and/or what slashdot is doing.
You can lead a man with reason but you can't make him think.
Browsers like Google Chrome and Microsoft Edge saw the abuse and acted by moving in to block the loading of data URIs inside the URL navigation bar. Now, Mozilla is doing the same for Firefox.
Nothing new
Please keep moving. Nothing to see here.
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
A better headline is actually a paragraph header half way through TFA:
"Firefox joins Chrome and Edge in blocking navigational data URIs"
So basically Firefox is simply implementing what is already standard practice otherwise on competing browsers.
Were he actually touching her breasts, you'd not be able to see the shadows beneath his fingertips, genius.
The more I realize that I can just import my bookmarks into Chrome and treat FF like I did with the netscape browser so many years ago. Remove the app and forget about it.
The major thing that makes me want to ditch FF is that the extensions and addons in chrome won't just stop working all at once like it will with 57.
Why do you feel the need to tell us that?
I personally found 57 to be the best thing ever, and none of my extensions broke because I was ready for this update 6 months ago. BUT you don't hear me yelling about it on a has-been tech forum.
Anyway thanks for sharing, now fuck off to Chrome.
Found the Mozilla developer in the thread.
that makes perfect sense - if you want to view the content made by an advertising company it would be totally insane to do it on a browser made by another advertising company.
better option: disable all DRM bullshit, boycott companies that depend upon DRM (and bribe it into web standards), and refuse to watch their programs.
if you really must view videos made by such a company, there's always bit torrent.
Anyone mod parent up? An extension framework that can sandbox extension to be 100% safe is a framework that can do nothing useful. Babysitting always fail at the end. We can only make it permission-segmented enough and hope the users understand what such and such permissions imply.
And how does hosts file block data: URIs, if there's no host to resolve?
P.S. I am happy you saw and answered my reply.