Skip to content

webapp: Be more lenient when browse lookup origin input is wrong (on optional parameters)

When browsing a revision, providing the wrong optional parameters, results in a 404 even though the main url is correct (without parameters).

Example:

https://archive.softwareheritage.org/browse/revision/a27a59f6b14c9fb13a6f998d8316628dafc1f60c/?origin_type=deposit&origin_url=https%3A//hal.inria.fr/hal-01727745

renders a 404 not found because the origin_url is wrong.

It should have been https://archive.softwareheritage.org/browse/revision/a27a59f6b14c9fb13a6f998d8316628dafc1f60c/?origin_type=deposit&origin_url=https%3A//hal.archives-ouvertes.fr/hal-01727745

Still, being more concilient in that kind of error would be more user-friendly.

Probably proposing something along the line of we did not find exactly that, maybe you meant that?


Migrated from T999 (view on Phabricator)

Edited by Phabricator Migration user
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information