[Ietf-caldav] Fwd: Summary of ETag related issues in RFC2518bis
helge.hess at opengroupware.org
Wed Dec 21 12:17:55 PST 2005
On 21. Dez 2005, at 17:39 Uhr, Lisa Dusseault wrote:
> It turns out HTTP has had, all along, a response code very suited
> to the server munging data on PUT: the 205 response. Yves Lafon
> pointed it out.
> 10.2.6 205 Reset Content
Hm. The explanation of 205 says something different, but I assume its
title (reset content) is close enough to be used for our purposes?
According to the content of spec item 10.2.6 the "reset content" has
nothing to do with a cache or the entity which was uploaded. The
"reset" applies to the referer page, not to the actual entity:
"view which *caused* the request to be sent"
In the context of CalDAV one might interpret the spec as "if an event
editor performs a PUT due to a 'save' button and the server returns
205, the event editor should be cleared".
But as mentioned, I think its close enough if its explained in CalDAV.
> Should we reference this in CalDAV?
Yes, definitely. Any server which modifies content will be required
to respond with a 205 (with an etag?!).
More information about the Ietf-caldav