We need a DeFi subnet

[paulyoung]

@dieter.sommer

However, an extension of the icx-proxy is currently being built that will allow a canister to “upgrade” a HTTP request from a query to an update call.

This got merged a couple of months back:

feat: upgrade HTTP calls upon canister's request

There is some uncertainty around whether is functionality is live yet. I’ve been focused on other things and haven’t gotten around to trying it on the IC proper.

Feature request: map appropriate HTTP request methods to update calls

Is this live already? If not, what is the ETA? I’m eager to migrate my telegram bot to this interface and disable my own AWS-Bounday-Node (which had this feature for a year now… ;-))

The "Body does not pass verification" error from a Motoko canister

I’m still a bit confused as to if this is natively handled or if it only works with the ICX proxy. Will this get hit for any HTTP request that is not a get natively? My particular use case involves images and having them return in query time is pretty important. Waiting for consensus is going to make the page crawl.

Feature request: map appropriate HTTP request methods to update calls

Hey @paulyoung,I see it has been merged into icx-proxy. But I use the following method to deploy on the main network, but it doesn’t work. Do I need to do anything else? Or must it only be used in icx-proxy? public query func http_request(request : HttpRequest) : async HttpResponse { { status_code = 200; headers = []; body = Text.encodeUtf8("Response to " # request.method # " request (query)"); streaming_strategy = null; }; }; public shared func http_reque…

Feature request: map appropriate HTTP request methods to update calls

I am fairly certain this hasn’t been rolled out. I checked the update logs and I know for sure about an unrelated issue blocking production upgrades. I will pull the built binary to ic stop gap repo. & update this thread when prod is up. (This week)