Skip to content

service: Fix possible error when looking latest origin visit

When an origin did not get visited yet, an error was raised when calling the service.lookup_origin_visit_latest function.

Also add a test to ensure the /origin/visit/latest/ endpoint of the web api returns a 404 status code when no visit exists for an origin.


Migrated from D2256 (view on Phabricator)

Merge request reports