Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use 410 Gone for deleted documents #103

Closed
kjetilk opened this issue Oct 29, 2019 · 3 comments
Closed

Use 410 Gone for deleted documents #103

kjetilk opened this issue Oct 29, 2019 · 3 comments

Comments

@kjetilk
Copy link
Member

kjetilk commented Oct 29, 2019

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.

@csarven
Copy link
Member

csarven commented Oct 29, 2019

#72 (specific case)
#46 (reuse)
#14 (privacy)
#41 (delete)
#61 (memento)

@csarven csarven added this to the March 19th milestone Oct 29, 2019
@timbl
Copy link
Contributor

timbl commented Jul 27, 2020

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.

I propose dropping this suggestion.

@csarven
Copy link
Member

csarven commented Aug 3, 2020

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.

@csarven csarven closed this as completed Aug 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

3 participants