[Seaside-dev] handling unsupported http methods
Julian Fitzell
jfitzell at gmail.com
Thu Nov 27 23:30:00 UTC 2008
Sounds reasonable. The ServerAdaptor definitely shouldn't be blocking
those, I'd say. It should be up to a request handler to decide and
since Application is the first request handler in the chain that knows
that it only wants GET and POST, that seems like the right place to
deal with it.
Julian
On 11/27/08, Philippe Marschall <philippe.marschall at gmail.com> wrote:
> Hi
>
> I recently went over the Swazoo server adaptor code. Since Seaside
> only supports GET and POST it returns 501 on any other method. I
> thought that was very clever. I don't think that any more.
>
> The main problem is when somebody wants to use Seaside for something
> else than it's intended and implement PUT, DELETE or whatever. If we
> catch that in the sever adaptor then we prevent them from doing that.
> So the best place to check would IMHO be WAApplication.
>
> What do you guys think?
>
> Cheers
> Philippe
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
More information about the seaside-dev
mailing list