We’re facing huge struggle with the fact, that we cannot easily retrieve multiple assets for the web frontend. What we need is a canister, which is able to resolve arbitrary files by calling https://<canister_id>.ic0.app/path/to/asset.js or something comparable. Are there any plans or ideas on this …

Is that how an asset canister knows to call its retrieve function when accessed by a url? by the creating of the http_request-method on the canister? Does this mean we can fully customize our asset canisters as if they were regular canisters? Im curious how the asset canister compares to a regular …

“Asset canisters” are just normal canisters whose primary purpose happens to be to store your frontend assets, but there is no special treatment on the protocol level.

Cool, thank you. So where did the 2mb file limit on the asset canisters come from? (I know now there is no 2mb file limit with the new beta release) My main question is will we have to use webpack for our frontend going forward? Or will we be able to just store the frontend-files-bytes on a canist…

Hi there - I was refraining from answering this question until I had signoff to make this post: Preview - Improved Asset Canisters . TLDR - we are supporting HTTP GET requests like a classic server now out-of-the-box! The 2mb file limit came from a restriction on message sizes that came from wasm, h…

Ah, sorry for the confusion. I was just referring to the CLI input from the Clap struct macro in the PR linked above, not for the actual release implementation. Just trying to understand the inner workings of ICP’s architecture as best as I can. From what I can infer from what you said, a developer…

The 2mb file limit came from a restriction on message sizes that came from wasm, however we’ve worked around it by supporting chunking in DFX. This is not entirely accurate: The 2MB restriction on message sizes is in “the replica”, i.e. the Internet Computer implementation. WebAssembly itself has…

:Gratitude for the clarification. I comprehend the need for the system message size limit, so now my question is with your statement here: so this chunking in the HTTP Gateway is a great way to avoid issues here. Where is the chunking happening in the specific? is it in the dfx tool? where the d…

The dfx SDK is able to chunk requests and send them to an asset canister. That canister is programmed to receive chunked files and to respond to http_request calls with chunked responses. You could implement the same functionality in your own canister, but it won’t be present on all canisters, just…

[image] levi: lets say the file is stored on my canister as bytes, if the whole file is 50mb, lets say a user requests the file with a public function update call, should the public function on the canister return with the whole mount of the bytes? or would i need to implement chunking on the ca…

[image] anon74414410: Even better news - this code is open source! The code to upload chunked assets lives in ic-agent and the http_request interface lives in ic-utils/src/interfaces/http_request.rs. GitHub - dfinity/agent-rs: A collection of libraries and tools for building software around the…

Can we somehow achieve or build a canister with a interface bahaving like a classic web server

Developers

nomeata May 25, 2021, 7:26am 55

(removed, moved to Feature request: map appropriate HTTP request methods to update calls - #2 by nomeata)

Topic		Replies	Views
Feature request: map appropriate HTTP request methods to update calls Developers	56	6105	April 22, 2022
Exposing URLs for querying images Developers	20	2088	May 16, 2022
Make external (non-IC) HTTP request from backend canister? Programs & Applications	5	4730	May 7, 2021
How do you call http_request on localhost? Developers Functional-Programming	34	4664	January 7, 2025
Query Api Endpoint? Developers	19	1020	January 30, 2023

Can we somehow achieve or build a canister with a interface bahaving like a classic web server

Related topics