I agree, that we might want to wait for a real-life request. On the other hand it is not only the end-users fault if not the correct methods could be used, though browsers are probably the major number of culprits. Many times it is just a question of firewall limitation which can by no means be circumvented by the casual user on the internet ...
Regards Felix Am Dienstag, den 16.10.2007, 10:47 -0700 schrieb Roy T. Fielding: > On Oct 16, 2007, at 1:18 AM, Bertrand Delacretaz wrote: > > > On 10/15/07, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote: > > > >> ...We could for example define that adding a "slingMethod=PUT" > >> parameter > >> to the request causes SlingServlet.doPut to be called instead of > >> doPost.... > > > > To clarify, note that I meant this for the POST method only, this > > should *not* be done with GET or HEAD. And we're still discussing if > > this should be done at all, see the "Actions (methods) must not appear > > in URIs" thread started by Roy. > > Unless you have an immediate customer need for it, we should not. > That is the kind of thing I would only do in combination with > a very specific user agent string, such that they would see their > bug when they tested newer versions of the user agent (at least > until they remove the restrictions from the browser setting of > header fields). > > ....Roy >
