Status ok when querying wrong filter endpoint

linksmart / historical-datastore

Lightweight time-series storage on the Edge of IoT

Apache License 2.0

13 stars 2 forks source link

Status ok when querying wrong filter endpoint #80

Closed farshidtz closed 4 years ago

farshidtz commented 4 years ago

Querying the following wrong path (extra filter section), responds with empty body and 200 status code.

curl --location --request GET 'https://localhost:8085/registry/filter/many/name/prefix/example' -i
HTTP/1.1 200 OK
Content-Type: application/json;version=master
Content-Length: 0
...