Globbing should return 200 OK even if empty

まず、/notes/note-* のような glob リクエストに対するサーバーの GET 処理を追跡し、既存リソースの場合と空のコンテナの場合を比較します。空のマッチがどのように 404 に変換されるかを確認し、そのうえで、一致するリソースがない既存のコンテナが空のリストとともに 200 OK を返すことを示すテストを追加します。

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.