[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cherokee
Subject:    Re: [Cherokee] Cherokee and WebDAV
From:       David Beitey <david () davidjb ! com>
Date:       2012-09-25 23:32:01
Message-ID: CAFXTrfbaKKCg+ktomuU8iSS=b0hw7Pv+D7HTEN-b203mxo9RFA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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 <david@davidjb.com> 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
> 


[Attachment #5 (text/html)]

In case anyone was curious about the status of this support for a HTTP reverse \
proxied WebDAV client in Cherokee, the recent fixed I&#39;ve made with regards to \
HTTP method handling take care of this.  The issue was that various methods -- see <a \
href="https://github.com/cherokee/webserver/commit/e6d7fa953822f7f7747c3a1324301f17dba \
7219a">https://github.com/cherokee/webserver/commit/e6d7fa953822f7f7747c3a1324301f17dba7219a</a> \
for details on which were affected (there were quite a few WebDAV-related methods) -- \
weren&#39;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.  <br>

<br>This fix is now in the latest version of Cherokee on GitHub and Cherokee has a QA \
test to check this in future.<br><br>-- David <br> <br><br><div \
class="gmail_quote">On 30 April 2012 14:46, David Beitey <span dir="ltr">&lt;<a \
href="mailto:david@davidjb.com" target="_blank">david@davidjb.com</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex">

All,<br><br>I&#39;m presently trying to host a WebDAV application behind Cherokee \
(reverse proxy) and communication works, except that the WebDAV client needs to send \
an &#39;If header&#39; and this header is seemingly being dropped within Cherokee.  \
This page: <a href="http://www.webdav.org/specs/rfc2518.html#rfc.section.9.4.5" \
target="_blank">http://www.webdav.org/specs/rfc2518.html#rfc.section.9.4.5</a> \
mentions 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?<br>


<br>Thanks in advance.<span class="HOEnZb"><font color="#888888"><br><br>-- David<br>
</font></span></blockquote></div><br>



_______________________________________________
Cherokee mailing list
Cherokee@lists.octality.com
http://lists.octality.com/listinfo/cherokee


[prev in list] [next in list] [prev in thread] [next in thread]