For the 2nd successful case, to be 100% sure I converted the received file into base64 string and then I checked how the file looks like in. When I run the debug mode, in each case I found that either: UploadAppraisalFile endpoint was never reached or if it was reached then always the full file was sent. uploading a file and then, in the Chrome browser, in the Network pane, change the uploading speed to a very minimum, then submit the form and then immediately close the browser.uploading a big file(about 16MB) and then suddenly after submitting the HTML form immediately close the browser window.To produce such an issue/edge case I tried: My idea was to count the file size at the point where the file is uploaded, add the information about the file size as an extra HTTP-HEADER (I called it Complete-File-Size), and then when the request reaches the backend, count if the received file size is exactly the same as the Complete-File-Size. I'm trying to prevent an edge case when somebody performs a POST request against my API UploadAppraisalFile endpoint and suddenly loses an internet connection which would result in sending a request with not the full file content. Return StatusCode(StatusCodes.Status411LengthRequired, 'Complete-File-Size header doesn't much received byteArray size') Logger.LogDebug('Complete-File-Size header doesn't much received byteArray size', file.Length, completeFileSize, inputAsString) Var inputAsString = Convert.ToBase64String(stream.ToArray()) If (file = null || file.Length != completeFileSize) Int.TryParse(completeFileSizeHeader, out int completeFileSize) Var completeFileSizeHeader = Request.Headers intermitent code change to investigate and validate Complete File Size and Actual File Size Public async Task UploadAppraisalFile(int appraisalID, string fileSubjectCode, IFormFile file)įile = file ?.FirstOrDefault() Please try to upload images/videos of a specific aspect ratio File upload *Only PDF, MP4, WEBM, OGG, JPG, JPEG, & PNG files are allowed.

Sharex discord embed