Calendar endpoint should return not-found status if given invalid CA name
Steps to reproduce
Steps to reproduce:
With an authenticated session, request calendar for an invalid CA (not registered), e.g.
http 200 response with empty calendar is returned
Endpoint should return http 404 (not found), consistent with REST.
Workaround (if any):
On reflection, I don't think this is a real issue. The capture agent id and series id are filters, and the API docs don't promise a 404 if they aren't valid, so the behaviour is consistent with the description.
We should double check this once PR 1597 (the new scheduler) goes in. I'll do that.