From my testing, /.well-known/ic-domains call must be a certified query call instead of an update call when registering a custom domain (the boundary node check seems to require it). Is there a reason for this?
It kinda makes sense from an asset canister perspective, but less so from an API perspective
In general I have struggled with handling dynamic query certification via code (vs asset canister file upload) and generally default to update calls to avoid needing to certify and store that in code
Hey @Gekctek
Yes, /.well-known/ic-domains must be properly certified or custom domains won’t accept your registration. We actually never considered to just do some update call as the custom domain is meant for “frontend” canisters, so canisters that implement the http_request method. Also, the custom domain enforces certification, so the requirement for that asset just means adding another certified asset to the rest.
What is your use-case for which you cannot provide a certified response and would prefer an update call?
1 Like
Well i am running an HTTP api canister with no frontend
Just in general its difficult to do HTTP api canisters because it seems the focus is frontend asset canisters or candid/IC api cansiters
It also seems like one can’t register a custom domain with a raw/api canister url which complicates things further