-
Notifications
You must be signed in to change notification settings - Fork 324
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
Can no longer temporarily disable redirect in menu #910
Comments
Hi @NatoBoram -- Global redirect toggle is no longer in the menu, but is still available in the preferences: |
That doesn't really help. To maintain a public gateway, I need to be able to quickly switch off the redirection and turn it back on when I'm done. Otherwise, I have to turn off the extension completely, but that means I won't be able to test the IPFS API on an IPFS website from my public node. |
@NatoBoram I am often testing resources with and without Companion too, but I use Incognito mode for that, and that is what I suggest in your case too. You can open Incognito mode via browser menu or keyboard shortcut – it is faster than toggling companion via its menu. Rationale: Companion does more than a simple redirect now (eg. network/http recovery amongst other things) and testing with disabled redirect alone can give you false results in some scenarios. You need to disable Companion to have confidence in testing. IPFS Companion is disabled in Incognito mode, so you don't need to toggle anything to get redirect back, just close Incognito tab. I hope this helps in speeding up your testing workflow. Unfortunately having two redirect toggles in main menu proved to be confusing to less technical users, so we are not planning on bringing it back, espcially when Incognito mode is much better for reliable testing. |
It's no longer possible to quickly prevent IPFS-companion from redirecting a public gateway's URL to localhost whilst keeping other interactions.
To Reproduce
Expected behavior
"Disable redirect" should be there.
Screenshots
Desktop (please complete the following information):
Additional context
This is very valuable to troubleshoot custom public gateways. If the extension is now all-or-nothing, then it's completely useless to any public gateway maintainer.
The text was updated successfully, but these errors were encountered: