Certified assets canister: Body does not pass verification when file splited

[flyq]

I use this certified assets canister and then use icx-asset to upload images:

icx-asset --pem ~/.config/dfx/identity/icp/identity.pem --replica https://ic0.app sync lxvgu-hiaaa-aaaag-qagaa-cai .

I found that if the image is smaller than 1900000 bytes, it will be uploaded in its entirety and accessed normally:

https://lxvgu-hiaaa-aaaag-qagaa-cai.ic0.app/music.jpeg

and if the image is larger than 1900000 bytes, it will be split into pieces and uploaded. But it cannot be accessed normally. I suspect that there is a problem with the assembly.

Here is a similar phenomenon:

Http_request streaming callback does not stream chunks anymore

My implementation of the http_request_streaming_callback does not work anymore - i.e. I only get the first chunk of data. For example this image gets truncated, the response length is 70000 instead of 1115313 (two chunks in memory, one of 70000 + 415313). The workaround is still valid? or was the candid issue has been solved Fix ty() for reference · Issue #273 · dfinity/candid · GitHub? [Capture d’écran 2022-03-04 à 14.52.40]

[3cL1p5e7]

Canisters are not yet able to certify chunks, and boundary nodes and the service-worker do not check chunk certificates, respectively.
There is topic about same problem

Boundary node http response headers

GitHub issue: https://github.com/dfinity/certified-assets/issues/10 I’m getting near the end of implementing partial responses for asset canisters, which allows more advanced streaming of audio and video content. My solution is working well locally, and I’ve deployed the new asset canister to production. The problem is that in production the partial responses no longer work. There are a few response headers that are key to getting this to work, Content-Range and Accept-Ranges. I wonder if the …

I even prepared a draft solution for this problem, but it has not been reviewed yet

feat: ic-certified-assets. Add chunk trees for certification

Let’s hope that dfinity-team will pay attention to this problem

[flyq]

So is there any good solutions?
my requirement is

• Ability to deploy a single image of around 2.5 MB into the IC canister
• Can be accessed through xxx.ic0.app/xxx.png.

Many thanks.

@3cL1p5e7

Let’s hope that dfinity-team will pay attention to this problem

@diegop