0041-00000101

Updated at:

Problem description

A mirroring-based back-to-origin request fails because the origin server returns an HTTP status code other than 200, 206, or 404.

Causes

When an exception occurs on the origin server, it returns an HTTP status code that OSS cannot process as a valid back-to-origin response, causing the request to fail.

The following table shows how OSS handles each category of origin response:

HTTP status code from originOSS behavior
200, 206Success
404Object not found
All other codesError — the mirroring-based back-to-origin request fails

Examples

None

Solutions

Check whether the origin server is working as expected.

  1. Send a direct request to the origin server URL using curl and check the HTTP status code it returns:

    curl -I <origin-server-url>/<object-path>

    If the response code is not 200, 206, or 404, the origin server is returning an unexpected status code.

  2. Check the origin server logs for errors, such as 5xx (server errors) or 3xx (redirects), that could explain the unexpected response.

  3. After resolving the origin server issue, re-trigger the mirroring-based back-to-origin request to confirm it succeeds.

References