Why not use something like custom headers like X-HTTP-Method and a
servlet filter to wrap PUTs in POSTs?
As we control the client API, this is a cleaner way to do this IMHO.
Lars
On 12.12.2007, at 17:29, Bertrand Delacretaz wrote:
That's why MicrojaxPostServlet uses a POST to /foo/* to
I think this is the best proposal,
put the 404.esp (or 401.esp or 500.esp for this purpose) into the
content tree, and all matching errors will look for a script ascending
the content tree. If nothing can be found, the default servlet kicks
in and shows a plain error message.
regards,
Why not use something like custom headers like X-HTTP-Method and a
servlet filter to wrap PUTs in POSTs?
As we control the client API, this is a cleaner way to do this IMHO.
but we do not control the client. the goal is to use simple html forms...
--
