Skip to content

CORS errors on getBinaryContent goes unnoticed #37

@JulienFS

Description

@JulienFS

The commit 3c17932 replaced the isLocal check by a status check for 0.
Local files return a status of 0, but same goes when there's a CORS error preventing a remote request to be executed.

Requests with CORS errors are reported as successful with an empty content.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions