You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It just occurred to me that if we retain server-controlled metadata #65 , then it would be trivial to return 410 Gone for resources that have been deleted.
The text was updated successfully, but these errors were encountered:
I would strongly argue against this, as it increases the distance between a unix file system and a solid one. I do not want my server to have to track things people have deleted.
It is also a potential privacy problem, in that a user can currently expect that filename (which can of course be embarrassing) is gone when they delete the file itself.
Based on my review of the issues listed in #103 (comment) and the current direction of the spec, servers are not required to return 410 for deleted resources. 410 is currently only mentioned for some cases in non-normative language.
Unless there is a reason to prohibit servers from ever returning a 410, which is I think a stronger position than what @timbl outlined, I agree to drop the suggestion.
It just occurred to me that if we retain server-controlled metadata #65 , then it would be trivial to return
410 Gone
for resources that have been deleted.The text was updated successfully, but these errors were encountered: