Hi Cameron, Thank you for your reply.
As far as I understand, the bug was closed because the editor stated that some interactions between browsers and web servers were not really defined, and that there would be conflicting use cases, in the case of a PUT or a DELETE request. In my mind, this may be true to some extent. For example, let's say I'm browsing my blog backend, opening the latest post page, and sending a successful DELETE request. If the server replies with a 204 (no content) response, what should my browser do? Nothing? Redirect to post-list? Is there a list of conflicting use-cases? What is the state of the draft proposal? Can I help in some way? Regards. -- Thibault Jouannic Ingénieur web freelance +33 (0) 6 30 47 30 50 http://thibault.jouannic.fr On Fri, 9 Dec 2011 15:14:57 +0000 Cameron Heavon-Jones <[email protected]> wrote: > I reopened the bug earlier this year prompted by requests from this mailing > list. since we've been working on a draft proposal and also addressing > concerns from Julian who initially created the bug. the most recent > discussion can be found on public-html[1] which was started by yet another > request to revisit.
