Open Bug 1452191 Opened 5 years ago Updated 3 years ago

Support eepsites (.i2p)


(Core :: Networking, enhancement, P5)

59 Branch





(Reporter: public, Unassigned)


(Whiteboard: [necko-triaged])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180323154952

Steps to reproduce:

Tested an eepsite.

Actual results:

It didn't work as expected: "Server Not Found"

Expected results:

Firefox once reconfigured _can_ connect to eepsites (.i2p) but then it can't use normal TLDs (eg .com, .org, etc). I suggest that Firefox uses separate configurations for .i2p sites.
Summary: Support Eepsites (.i2p) → Support eepsites (.i2p)
Severity: normal → enhancement
Component: Untriaged → Networking
Product: Firefox → Core
Priority: -- → P5
Whiteboard: [necko-triaged]

Hi, I saw this bug when looking for information about I2P configuration in need of updating. I have spent much of the past six months on a way to provide a UI for I2P that works relatively seamlessly within Firefox almost exactly as described in the original issue. It is my opinion that at this time, this can mostly be handled adequately in WebExtensions, and that as more Tor patches are incorporated into Firefox, a WebExtension based approach will become the preferred method for configuring I2P. Our problem and Tor's aren't identical, but they are certainly similar enough that I2P users benefit from their work even more than the internet at large. Besides needing to enable fingerprinting resistance, container tabs, first-party isolation and other privacy features, there is quite a bit more to I2P than the eepWeb, there is potential for things like torrents-over-I2P in the browser for which proxy-only configuration is inadequate but which can be done in an extension. I don't think incorporating this functionality into Firefox directly is the right way to go.

You need to log in before you can comment on or make changes to this bug.