Location Error about ngx-uploadx

[kukhariev]

Backend must set the Location header:
uploadx api,
google drive api

If there are difficulties in implementing this apis you can use ready-made solutions such as tusdotnet,
or sometimes it's easier to create your own custom uploaderClass to support a non-standard upload api.

Chunk index custom uploaderClass example:

// uploaderXwithChunkIndex.ts

import { UploaderX } from 'ngx-uploadx';

export class UploaderXwithChunkIndex extends UploaderX {
  chunkIndex = 1; // init

  async sendFileContent(): Promise<number | undefined> {
    const { end, body } = this.getChunk();
    const headers = {
      'Content-Type': 'application/octet-stream',
      'Content-Range': `bytes ${this.offset}-${end - 1}/${this.size}`,
      'Chunk-Index': this.chunkIndex
    };
    await this.request({ method: 'PUT', body, headers });
    
    this.chunkIndex++; // increase on success

    return this.getOffsetFromResponse();
  }
}

add to options:

  options: UploadxOptions = {
    endpoint: `${environment.api}/files`,
    ...
    chunkSize: 10 000 000,
    uploaderClass: UploaderXwithChunkIndex
  };

[cormac01]

Thanks for the above. This was helpful documentation. Have fixed backend and am returning Location as suggested but am still receiving error. See below execution plan and response.

1. upload request sent to "https://localhost:44357/api/Uploads/Uploads". This works fine and hits controller.
2. In by backend I have Location header set for PUT endpoint like so: HttpContext.Response.Headers.Add( "Location", $"https://localhost:44357/api/Upload/SendChunk?uploadId={uploadId}");
3. In my client I can see the response headers which contains Location, see below:
   
4. Unfortunately, I am still getting initial error mentioned like so:
   

Can you see anything immediately obvious - bad url or http protocol must be HTTP. Thanks for any assistance.

[cormac01]

@kukhariev found the issue, issue with cors policy in my backend and needed the below header. thanks for the help.

[kukhariev]

Yeah, I saw that, and we also need to remember to add Range to the Access-Control-Allow-Headers header for PUT requests.
Or context.HttpContext.Response.Headers.Add("Access-Control-Allow-Headers", "*") ,
or take it from browser access-control-request-headers

[cormac01]

cheers @kukhariev