My understanding right now is that if a developer chooses to expose canister functionality through http_request and http_request_update, that they essentially forgo all certification. It would be great if some kind of certification information could be returned in response headers so that http clie…

There is a header to set for certification. There is a v1 and v2. https://internetcomputer.org/docs/current/references/http-gateway-protocol-spec#response-verification-outline The reason rest based services are such an issue is that they are typically unbounded in variability and there is no way to…

When I was doing the farcaster frame in Motoko it seemed like http_request query calls you could add a cert header, if you ran in through http_request_update first, then cached it. And the http_request_update should run through consensus and create it for you, but I have only played with it a little…

Late to the party but I have a follow up question. Consider a canister that update http queries to http updates. How can we have 100% certainty that we went through consensus? The node that received the query could very well have intercepted the call and returned some locally-generated results with…

If the subnet signs it with is key, it has to go through consensus. These signed responses can either come from a update call OR a query call that has the static http response+signature cached A query call can’t do that on is own, but the first time it’s called (assuming it’s static content), the r…

Thanks. I’d like to understand how http update calls are implemented. Is it correct that from the outside (client), http query and update calls are similar. When the http calls hits the IC, it is first handled by a single node. And only if it is an update calls more nodes will be involved for consen…

The client handles them differently through the boundary nodes. With a query call, its just a call to one replica through the node, but the update calls are a call with read_state polling. But the result is essentially the same. Im not sure on the specifics of how the boundary nodes handle calling …

If the initial request returns upgrade = Option<true>, the system will “upgrade” the query into a call, and will use the http_request_update method. You can use that method to do your work, calculate a certificate, and cache the response as well as the certificate. This is the pattern that I call a …

Cool! How can the certification be checked by the external party (the caller)?

Actually, this is in progress of development to make it easy to use. Small talk about this was here: [image] Pluto - HTTP router & SSR tool Showcase Improved version: Did you need to share data via HTTP on ICP? Or perhaps you want to create an SSR website and limit the c…

@dfinity/certificate-verification - npm or ic_certification - Rust

Http_request and http_request_update certification

Developers

pu0238 March 28, 2024, 10:49pm 10

Actually, this is in progress of development to make it easy to use. Small talk about this was here:

Topic		Replies	Views
Canister as REST Server - Certification Questions Developers	5	101	February 1, 2025
Feature request: map appropriate HTTP request methods to update calls Developers	56	6329	April 22, 2022
[Discussion] Data certification on IC Developers	6	1940	September 19, 2022
Cannot find a good example how to handle HTTP POST in Rust(update) Developers rust	3	283	January 31, 2025
How do some canisters handle http requests Developers	2	2070	January 24, 2022

Http_request and http_request_update certification

Related topics