Skip to content

Downloading of Artifacts return 502 when upstream returns 404 (for all ecosystems except Go) #208

Description

@Tilian

When an upstream registry answers 404 for an artifact download, the proxy responds 502 Bad Gateway instead of 404 Not Found. #184 fixed this for the Go handler only but every other ecosystem is still affected.

This can result in package managers treating the repository as broken instead of continuing resolution.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions