Oh sorry, I thought you asked for one of the Accept headers... The good answer is that we don't support "Allow" yet, but this must done as part of this issue:
"Server Capability Description in Call interface" http://restlet.tigris.org/issues/show_bug.cgi?id=107 Here is the battle plan: - add a method to Call: getAllowedMethods() : List<Method> - add a method to Resource: * allowGet() : boolean (false by default) * allowPost() : boolean (false by default) * allowPut() : boolean (false by default) * allowDelete(): boolean (false by default) * getAllowedMethods() : List<Method> The default implementation of Resource.getAllowedMethods() would test all the can*() methods and create the matching result list. Also, the Handler (to be renamed Finder), will test the allow*() methods on the target resource before invoking the matching get|post|... method and return a 405 status if necessary and set the Call.getAllowedMethods() with the result of Resource.getAllowedMethods(). Does it sound good? Best regards, Jerome > -----Message d'origine----- > De : Lars Heuer [mailto:[EMAIL PROTECTED] > Envoyé : jeudi 5 octobre 2006 14:18 > À : Jerome Louvel > Objet : Re: Allow Header > > Hi Jerome, > > > Only non-standard headers can be added via the special > attribute. The > > "Allow" header is supported at the API level by the > > Call.getClient().getAccepted*() methods. > > Thanks, that was one of the places where I looked, but I > cannot find a > way how to set, i.e. > > Allow: GET, PUT, OPTIONS > > Hints? > > Best regards, > Lars > -- > http://www.semagia.com > >
