Thanks Jerome,

Now's more clear.

On Mon, Jun 29, 2009 at 11:30 AM, Jerome Louvel
<jerome.lou...@noelios.com>wrote:

>  Hi Alin,
>
>
>
> The reason is simple: when a method is not allowed, HTTP expects the server
> to return the list of allowed methods, therefore the framework introspects
> the resource by calling allow*() methods.
>
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.6
>
>
>
> Best regards,
> Jerome Louvel
> --
> Restlet ~ Founder and Lead developer ~ http://www.restlet.org
> Noelios Technologies ~ Co-founder ~ http://www.noelios.com
>
>
>
>
>
>
>
>
>
>
>
> *De :* Alin Popa [mailto:alin.p...@gmail.com]
> *Envoyé :* mercredi 24 juin 2009 15:06
> *À :* discuss@restlet.tigris.org
> *Objet :* Restlet v 1.1.5 multiple times allow method checked
>
>
>
> Hi,
>
> Very soon I noticed something strange(?) when using Restlet Resources:
>
> if a http method is not allowed, it will go and check all allow methods:
> e.g.
>
> When using DELETE http method and only POST is allowed,  it will go and
> check
> allowDelete, allowGet, allowPut.
>
> Why is not doing just one check for allowDelete and stops ?
> Is this the normal behavior ? If yes, is there a way to suppress returned
> message within a Resource ?
>
>
> Thanks.
>
> --
> Regards,
>
> Alin
>



-- 
Regards,

Alin

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2366288

Reply via email to