-
Notifications
You must be signed in to change notification settings - Fork 16
Calls to /api
are no longer forwarded to the replica
#46
Comments
This is intentional - at least for secure domains such uncertified “holes” make your users attackable by a malicious replica. You should not use the canister domain for IC requests, but some generic domain (is it simply |
This is all abstracted away from me by By the way, I’m only using |
Ah, so maybe (just guessing) the agent has logic for picking the right gateway domain in production, but not locally. Hmmm. |
I think calls are made relative to the current domain, so if I do |
Right, that is the old behaviour that used to work, until the proxing of |
I’ll try upgrading |
That change won’t help you in the local use-case, I don’t know if any others changes there have. But worth trying, of course. |
Based on this post by @Daniel-Bloom-dfinity I think I need to set the @ninegua also shared something in this post about using Perhaps seeing |
Setting the host as described above appears to be working as intended. Thanks for the help! |
In addition to the above I had set the host to I think not setting the I still needed to forward |
I think the simple solution to the above is to use |
Ah, no, that's the default and that includes the subdomain. |
I upgraded
icx-proxy
from e3866f0 to 7624053 and now the initial call to/api/v2/status
returns the HTML page of my asset canister, and a CBOR decoder tries to decode that and throws an error.I downgraded back to e3866f0 API calls were forwarded again.
Is there some new flag I need to pass to get the old behavior? I couldn't see anything obvious in the help text.
The text was updated successfully, but these errors were encountered: