3 ms·
For example, suppose you want to distinguish between a missing/deleted resource /myuser/23123 and a completely invalid query /muser/23123. Both of these are 40
by paulddraper 7y ago
For example, suppose you want to distinguish between a missing/deleted resource /myuser/23123 and a completely invalid query /muser/23123.
Both of these are 404 (or 410 for permanent caching) responses according to HTTP, though they have very different reasons for "non-existance".
- wool_gather 7y agoNo, the "completely invalid query" is 400. 404 is only for "the request makes sense but that specific resource doesn't exist".
- paulddraper 7y ago400 is a very generic error. It is often used to complain about problems with the request body. Considering how brief the HTTP RFC is, your interpretation is I think as good as any, if very uncommon. (Not what Django, Rails, Flask, etc. do).
- akvadrako 7y agoIn this case it’s a 404 because the query URL pattern doesn’t exist - the most common cause of 404s.
- pavel_lishin 7y agoSame thing, no? If I ask for /api/user/238885 and I get a 404 back, it's because the resource "user" with ID of 238885 doesn't exist. If I ask for /api/banana/wharrgarbl, it's because the resource "banana" with the ID of "wharrgarbl" doesn't exist.
- deleted 7y ago[deleted]