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.

首先跟踪服务器对 /notes/note-* 等 glob 请求的 GET 处理，并比较现有资源和空容器这两种情况。确认空匹配如何转换为 404，然后添加覆盖测试，表明现有容器在没有匹配资源时会返回带有空列表的 200 OK。