If I read the HTTP1.1 spec correctly, PUT, as inherited by WebDAV, should support the Content-Range header or send a 501 (Not implemented) response. If I read the Slide 1 and 2 WebDAV code correctly, I don't see either happening. I can confirm, based on tests by my colleagues, that Slide 1.0.16 just ignores the Content-Range header and stores the range as if it were the whole content, but we haven't tried this with Slide 2.
If I'm missing something, or if there is work being done on this, please let me know. Otherwise, I'll look at submitting a patch (could be a while though). Thanks, Jim James Myers Computational Science and Mathematics Pacific Northwest National Laboratory
