[Solved] When using chunked upload the success response body is always empty

1 Answer 94 Views
Upload
Bram
Top achievements
Rank 1
Iron
Iron
Bram asked on 31 Jul 2025, 02:17 PM | edited on 31 Jul 2025, 05:44 PM

I am using the TelerikUpload component with UploadChunkSettings defined.
Telerik.UI.for.Blazor version 9.0.0

When not using a chunked upload I can return a response body a read it in the success handler, however when code was changed to use chunks the response body is always empty.

Is this a bug when using chunked upload, or do I need to return a different response in the Controller?

 

Code from the save method in Api Controller:

string chunkMetaData = formData["chunkMetaData"].ToString();

ChunkMetaData chunkData = JsonConvert.DeserializeObject<ChunkMetaData>(chunkMetaData);

// Append chunks to file
// ...


if (chunkData.TotalChunks - 1 == chunkData.ChunkIndex)
{
     uploadComplete = true;
     fs.Flush();
}

// More code omitted ...

if (uploadComplete)
{
	Response.StatusCode = StatusCodes.Status200OK;
	await Response.WriteAsync(result.ResultId.ToString());

	return new EmptyResult();
}
else
{
	Response.StatusCode = StatusCodes.Status201Created;
	await Response.WriteAsync("Chunk upload successful.");
	
	return new EmptyResult();
}

 

OnSuccess handler:

protected async Task SuccessHandler(UploadSuccessEventArgs args)
{
	int resultid = 0;

	if (int.TryParse(args.Request.ResponseText, out resultid))
	{
		//  do something with the resultid
		//  ...
		//  args.Request.ResponseText is always empty when using chunked upload
	}
}



Jonathan
Top achievements
Rank 1
Iron
commented on 27 Apr 2026, 06:42 PM | edited

According to the release notes for Telerik® UI for Blazor 13.2.0, this issue was fixed, but it doesn't look like it's actually fixed.

I am using v13.2.0, and am still seeing that the fields in Args.Request (ResponseText, ResponseType, Status, StatusText) are all null or 0 in the success handler when using chunked upload.

This works well with chunking disabled, but we need chunking to avoid file size/timeout restrictions. Any updates?

Dimo
Telerik team
commented on 28 Apr 2026, 07:23 AM

Please upgrade to version 13.3.0, which was released one day after 13.2.0. Version 13.2.0 has a problem with the JSInterop file, which affects some new features and fixes, including this one. Sorry about that.

Check the attached app.

1 Answer, 1 is accepted

Sort by
0
Dimo
Telerik team
answered on 01 Aug 2025, 12:43 PM

Hello Bram,

This was fixed recently and the changes will take effect in the coming release in two weeks.

Regards,
Dimo
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Jonathan
Top achievements
Rank 1
Iron
commented on 20 Apr 2026, 09:04 PM

@Dimo, your link refers to a different issue. The issue described by Bram is not fixed and continues to persist in versions 12 and 13.

All the fields in Args.Request (ResponseText, ResponseType, Status, StatusText) are all null or 0 in the success handler when using chunked upload.

It does work when chunking is turned off.

Dimo
Telerik team
commented on 21 Apr 2026, 01:49 PM

@Jonathan Hm, indeed, I thought the linked fix resolves both problems, but apparently not. A fix for this problem from this thread is now awaiting approval. It will be released either tomorrow or next month.
Jonathan
Top achievements
Rank 1
Iron
commented on 21 Apr 2026, 08:46 PM

Thank you @Dimo, that's good to know. Is there any workaround that you know of in the meantime? We'd really like to get chunked uploads working, it's a very useful feature.

Dimo
Telerik team
commented on 22 Apr 2026, 06:33 AM

Jonathan - we will release the fix today, so there is no need for a workaround (moreover, I am not sure there is one).
Tags
Upload
Asked by
Bram
Top achievements
Rank 1
Iron
Iron
Answers by
Dimo
Telerik team
Share this question
or