Skip to content

403 Forbidden does not emit error #3

@pguillory

Description

@pguillory

I set the wrong access key, causing S3 API calls to return HTTP/1.1 403 Forbidden.

Expected: s3 object would emit 'error' but not 'complete'.

Actual: other way around.

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