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.