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://testallinone.usask.ca/recordings/calendars?agentid=unknown

Actual Results:

http 200 response with empty calendar is returned

Expected Results:

Endpoint should return http 404 (not found), consistent with REST.

Workaround (if any):

Activity

Show:
Stephen Marquard
April 19, 2019, 1:56 PM

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.

Greg Logan
July 12, 2017, 3:08 PM

We should double check this once PR 1597 (the new scheduler) goes in. I'll do that.

Won't Fix

Assignee

Greg Logan

Reporter

Stephen Marquard

Severity

Incorrectly Functioning With Workaround