Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COOk, I want to differentiate 3 circumstances: a resource with some content, a resource with empty content, a resource doesn't exist at all. And I can see how your path-only url style perfectly maps them into: 200 with content, 200 with empty content (or perhaps a 204), and 404 not found. But now what if the url has to contain query string, like in my example? I just don't think all complicated query criteria can be arranged into path-only style.
      singulars
    2. COIf you have to use a sort of super resource that can be very different depending on query string I would stick with 200. How you convey no-news-yet or something along those lines is an issue outside of HTTP. It really depends on the media you are turning and what the client expects. For example in HTML you might simply say "No news yet", which a reader would understanding. But that is still content obviously since it is a HTML page. I wouldn't use 404 for a resource that exists but has changing content even if one version of that content could be no news.
      singulars
    3. CO"Super resource" is sometimes a natural choice if the service is kind of a search engine. 200 has a good point here. For example, do people or (author of) a program expect a sudden 404 when using google? Wouldn't that cause they think "did I just type a wrong host name or something"? And I like your saying **"I wouldn't use 404 for a resource that exists but has changing content even if one version of that content could be no content"**.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload