Globbing should return 200 OK even if empty

Assuming I have a container named /notes in my POD and this container contains resources matching /notes/note-* I get a nice list of those resources if I do a GET of /notes/note-*.

But if the /notes container is empty and I try GET /notes/note-* I get 404 - not found.

If think that is wrong, The container is there and any attempt to get a filtered list of its content should return 200 OK since the list is there (the container exists) but it is simply empty as there are no matching resources in the container.

Returning 404 tells the client "You made a mistake - there is nothing here". But the client did not make a mistake - it simply asked for an empty list, not a missing-non-existing list.

Comece rastreando o tratamento de GET do servidor para solicitações glob como /notes/note-* e compare os casos de um recurso existente e de um contêiner vazio. Verifique como uma correspondência vazia é convertida em 404 e, em seguida, adicione cobertura mostrando que um contêiner existente sem recursos correspondentes retorna 200 OK com uma lista vazia.