Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
fts-rest 3.9.4
-
Security Level: Public Data (This ticket is visible to anyone on the internet and will be indexed by search engines)
-
None
Description
This particular edge cases fails in the /jobs/<job_list> controller.
However, when the job list has more than 1 item, it will work.
Example (1 invalid job):
curl -s https://fts3-devel.cern.ch:8446/jobs/foo
<html>
<head>
<title>404 Not Found</title>
</head>
<body>
<h1>404 Not Found</h1>
The resource could not be found.<br /><br />
No job with the id "bar" has been found
</body>
</html>
Example (for 2 jobs):
curl -s https://fts3-devel.cern.ch:8446/jobs/foo,bar | jq . [ { "http_message": "No job with the id \"bar\" has been found", "job_id": "bar", "http_status": "404 Not Found" }, { "http_message": "No job with the id \"foo\" has been found", "job_id": "foo", "http_status": "404 Not Found" } ]
Handling should be the same even when the job list has only one invalid element in it.
