Skip to content

IPFS Desktop App Hijacking Web GUI & Caching Issue #1

@magiccodingman

Description

@magiccodingman

When the IPFS desktop app + the companion app is working. The IPFS Web GUI loves to try and communicate with local 127.0.0.1 which hijacks the communication. When the Web GUI is supposed to be a strict communication via the proxy. Which leads to your GUI interface showing what's on the desktop app, not what's on your server. There has been multiple changes to attempt to fix this without being too invasive. The changes have helped, but not fully resolved the issue.

Additionally browsers cache the index.html and manifest file aggressively. Which when stale can cause significant issues when this occurs. Majorly causing issues with getting a white screen and everything not loading due to the bad out data data. This doesn't always happen. But when it does, it's annoying.

I'm aware of these issues and still pondering how to resolve them. They're annoying quirks then detrimental. I've not always been able to get these behaviors to repeat either. The current method being utilized for the hijacking of the IPFS companion app and desktop app is within IpfsGate.Proxy in which when the index.html is being detected, it'll auto inject a special script and alter paths. It keeps everything still 100% as it should be, but it adds a script that without a service worker blocks and stops the 127.0.0.1 requests from going out.

I wanted to avoid a service worker because if a site loads via the /ipfs/ route or others that utilizes a service worker, it can be kind of annoying having it attached to the domain, not properly handled, or just a limitation that adding my own service worker will limit what you can load. And I don't want that.

Anyways, I know this is an issue, though simply switching browsers for a day often resolves this for now. Sadly blowing out cache isn't always the solution because browsers can be incredibly aggressive with caching to disk in ways you can't always control.

Update - 1
This bug is only occurring for me on Edge right now. I need to do more testing to figure out what's going on.

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions