Re: routes request

[Ben Bangert]

On Apr 2, 2006, at 1:29 PM, Kendall Clark wrote: Hmm, I don't think it should be 404, it should be 405: Agreed. 10.4.6 405 Method Not Allowed (No reason we can't write code to build the Allow header explicitly, based on the decorator value...) Yep, pretty easy to have it add that Allow header for the action. Does this suggest that @pylons.rest.restrict() should take a list? @pylons.rest.resrict("POST", "PUT"), so any other method returns a 405 with an Allow: header of POST, PUT: Sure, sounds good to me. Also makes it quite REST-ful as its indicating what methods are allowed for that URL. HTTP/1.1 405 Method Not Allowed Allow: POST, PUT Yeah? Yup. And, FWIW, I think I prefer @pylons.rest.dispatch() to dispatch_on(), but that's up to you. I'm good with dispatch as well. Right now, today, that doesn't bother me. :> Great, then I'll take a crack at implementing one, unless you'd like to give it a spin first. :) Cheers, Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [EMAIL PROTECTED] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss -~----------~----~----~----~------~----~------~--~---