Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Requests to IPFS via local gateway with Companion extension getting blocked #65

Open
chilledfrogs opened this issue Sep 26, 2020 · 0 comments

Comments

@chilledfrogs
Copy link

Hello all,

I recently noticed an issue with HTTPZ's HTTPS downgrade detection: it just plain doesn't seem to work when dealing with IPFS local gateway redirects.

The issue seems to stem from the fact that HTTPZ can't accept wildcard hostname expansions, which would be required to make a proper manual exclusion (since the IPFS Companion redirects all IPFS resources to either .ipfs.localhost:8080 or .ipns.localhost:8080). I have tested that indeed if I put the precise hostname, it of course works, but this isn't really feasible for each and every IPFS resource...

I'm a bit surprised though that it doesn't try to downgrade to HTTP automatically once it sees that it can't connect via HTTPS, if I understood correctly the basic functionality and am not completely blind, I thought it would 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant