In case anyone was curious about the status of this support for a HTTP reverse proxied WebDAV client in Cherokee, the recent fixed I've made with regards to HTTP method handling take care of this. The issue was that various methods -- see https://github.com/cherokee/webserver/commit/e6d7fa953822f7f7747c3a1324301f17dba7219afor details on which were affected (there were quite a few WebDAV-related methods) -- weren't configured to accept request bodies. So, headers would be received and processed by Cherokee, but not the body. This lead to my back-end application being confused as it was only receiving part of the expected request.
This fix is now in the latest version of Cherokee on GitHub and Cherokee has a QA test to check this in future. -- David On 30 April 2012 14:46, David Beitey <[email protected]> wrote: > All, > > I'm presently trying to host a WebDAV application behind Cherokee (reverse > proxy) and communication works, except that the WebDAV client needs to send > an 'If header' and this header is seemingly being dropped within Cherokee. > This page: http://www.webdav.org/specs/rfc2518.html#rfc.section.9.4.5mentions > this is the expected behaviour of HTTP for non-understood headers, > but is there some way to allow Cherokee to recognise this header and > prevent it from being dropped? > > Thanks in advance. > > -- David >
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
