bug #8770
NameControllers responds with all entities when name uuid is not found
Status:
Closed
Priority:
Highest
Assignee:
Category:
cdmlib-remote
Target version:
Start date:
12/16/2019
Due date:
% Done:
100%
Severity:
critical
Found in Version:
Description
When the uuid in portal/name/c0b7aa13-301d-4a0c-a8c6-843e96c34ba8/taxonNameDescriptions.json is not found in the db the controller rerturns all taxonNameDescriptions.
Instead the controller must respond with an http 404 code.
The same accounts for
-
/name/{uuid}/typeDesignations -
/portal/name/{uuid}/taxonNameDescriptions
Associated revisions
fix #8770 responding with http code 404 in case name uuid is not found
History
#1 Updated by Andreas Kohlbecker 9 months ago
- Subject changed from NameControllers repondt with all entities when name uuid is not found to NameControllers reponds with all entities when name uuid is not found
#2 Updated by Andreas Kohlbecker 9 months ago
- Status changed from New to Resolved
- % Done changed from 0 to 50
Applied in changeset cdmlib|cc3ce6e30c74308b6697f6007d03d37b00cce8ff.
#3 Updated by Andreas Kohlbecker 9 months ago
- Status changed from Resolved to Closed
- % Done changed from 50 to 100
fixed
#4 Updated by Andreas Müller 9 months ago
- Subject changed from NameControllers reponds with all entities when name uuid is not found to NameControllers responds with all entities when name uuid is not found
