Firefox 84.0

Post by bzbarsky » Wed, Dec 16, 2020, 4:43 AM UTC

Dylan16807 wrote: post #276

bzbarsky wrote: post #268

Earlier quoted context omitted.

What Mozilla is implementing here, I suspect, is RFC 6761 section 6.3 item 3, which says: Name resolution APIs and libraries SHOULD recognize localhost names as special and SHOULD always return the IP loopback address for address queries and negative responses for all other query types. Name resolution APIs SHOULD NOT send queries for localhost names to their configured caching DNS server(s). A few notes: 1) The use…

My reading is that the API Firefox calls into is responsible for not pinging the DNS server.

Post by jhatemyjob » Wed, Dec 16, 2020, 4:46 AM UTC

ksec wrote: post #134

chinhodado wrote: post #11

I love Firefox, I use it everyday, I can't imagine using a browser without Tree Style Tab, or all the things that I can do in about:config. At the same time, I can't shake off the dreadful feeling that it will eventually die one day. The market share keeps falling year by year. What is the most realistic future for Firefox?

>What is the most realistic future for Firefox? Realistic isn't a word I see often on HN. It wont die. Google will keep funding it just to say they dont have a monopoly in browser market. But it will continue its path towards irrelevant by mainstream usage. They will continue to shrink the engineering as budgets are cut. Until no more silly 20% project and management goals that drains resources ( they wont have that…

Post by dragonwriter » Wed, Dec 16, 2020, 5:07 AM UTC

bzbarsky wrote: post #280

rascul wrote: post #275

Earlier quoted context omitted.

> There's really no way to win here. In theory Firefox could do the resolution as normal and then if it doesn't come back as loopback replace it with 127.0.0.1. That would be perfectly within the letter of the RFC, since noneo f the stuff above it MUST-level requirements, but probably not really within its spirit, since it would violate the "SHOULD NOT" bit. Could a check to see if the name is "localhost" or "*.local…

> Could a check to see if the name is "localhost" or "*.localhost" suffice to satisfy the "SHOULD NOT" requirement? To satisfy that requirement you have to check for those names and if that's what the name is _not_ ask the "configured caching DNS server". Which means you need to do what? Calling OS APIs will do that DNS server thing unless the name is in /etc/hosts. You could manually parse /etc/hosts and see whether…

Post by Konohamaru » Wed, Dec 16, 2020, 5:17 AM UTC

bzbarsky wrote: post #91

nerdponx wrote: post #68

Earlier quoted context omitted.

Am I incompetent if I thought all browsers all did this already by default? Or was this typically enforced at the OS/networking-stack level, and now Firefox is adding an additional guarantee that it will happen directly in the browser, even if the networking stack would say otherwise?

The latter. You can always set your /etc/hosts or equivalent to map "localhost" to some random IP that is not loopback. Or a proxy could proxy that hostname, etc. In the new setup proxies can't proxy localhost unless you set a pref to explicitly let them do that, and for "localhost" and hostnames ending in ".localhost" Firefox won't even ask the DNS stack for the IP, assuming loopback instead.

Post by 3r8riacz » Wed, Dec 16, 2020, 5:50 AM UTC

cpeterso wrote: post #145

comprev wrote: post #30

Earlier quoted context omitted.

The only reason I use Chrome these days is for built in translation. Apart from that it's always FF.

Have you tried the "To Google Translate" Firefox add-on? It's not as seamless as Chrome's built-in translation but it works for me. https://addons.mozilla.org/firefox/addon/to-google-translate...