As a non-technical person, here is my cursory read on the above…
Download this peice of software to speed up connection to the IC and thus enhanced performance. The decentralization and greater control piece do not affect my user experience…
So my first question is, can I download this on mobile too? And secondly, I do not know how to download and run software from github. Will you make this more accessible?
There was an issue in OpenChat independent of the IC HTTP Proxy, which caused the same problem and should have been resolved. I just tried to reproduce it, but didn’t manage. For me it worked, with the IC HTTP Proxy. Could you provide is with more details, please: do you try to access OpenChat over oc.app or the canister URL
To download the software, just go to Github and click on either the “install mac OS X” or the “install windows” button (see screenshot) based on the operating system you are using. This will download the installer.
This is still a proof-of-concept and we are trying to gather community feedback. Therefore, we don’t have a mobile version yet. Based on the feedback, we will further improve the proxy and its user experience.
Hi @Mania, this proxy is still a proof of concept, the only supported platforms are Windows and MacOSX.
With that in mind, we’ve already tested how this would look like on mobile and it is possible to accomplish the same end result as with the Desktop proxy with a slightly different approach, however, at this stage we are collecting community feedback for the Desktop version, this will help improve it’s capabilities and user experience.
Once we have established a baseline of what capabilities it would need to offer, we can focus on making a stable release of this Desktop proxy version and after that focus on alternatives such as supporting mobile platforms.
@MillionMiles when you start the propxy, are you getting the prompt to enter your admin password?
You can also try launching the app from your terminal under: /Applications/IC HTTP Proxy.app/Contents/MacOS and see some logs in the console maybe that would give us a good indication of what is happening.
Thanks @MillionMiles! Unfortunately there’s nothing indicative of a problem there. Could you also check ~/Library/Preferences/dfinity/ichttpproxy to see if there’s any additional logs there that might be helpful? Feel free to DM me if you don’t wish to share them publicly on the forum.
This is a rudimentary question,
I’m not sure if the communication to the API boundary node is encrypted afterwards if you terminate TLS locally. Regardless of local termination of TLS,
are API calls from the HTTP gate way to the boundary node encrypted?
TLS is terminated locally to allow for translating standard web requests to a format that the IC can understand. The translated requests are then sent to the API boundary nodes through a new TLS connection so everything remains encrypted.
Thank you!
So you’re saying that the TLS termination at the HTTP Gate way has been replaced by a local one, so one of the centralized pathways has been eliminated, so one step more decentralized?
However, the Local → API Boundary node still requires a TLS connection and the message is encrypted and protected, but the centralization is not yet completely eliminated.
Yes that’s exactly right! Once the API boundary nodes are fully decentralized (which is in progress), using this proxy will be a fully end to end decentralized solution.