Results 64 comments of rhodey

awesome, thanks! I would expect curl to calculate the data length header itself and include this automatically but to check this try adding the `-v` option and this will show...

I think these two lines in the HTTP request are our problem: ``` Transfer-Encoding: chunked Expect: 100-continue ``` Our PROPFIND request is actually an XML document so technically we're sending...

`$ man curl` > Remove an internal header by giving a replacement without content on the right side of the colon, as in: -H "Host:" try adding a `-H "Expect:"`...

got it :D, kinda... :| ### request ``` bash curl -k -i -u : -X PROPFIND https://webmail.web4all.fr/.well-known/carddav --upload-file - -H "Depth: 0" -H "Content-Length: 105" -H "Transfer-Encoding:" -H "Expect:"

@taiyed I was just able to reproduce this error while testing Flock compatability with OwnCloud which uses SabreDAV. Changing the namespace from "org.anhonesteffort.flock" to "http://org.anhonesteffort.flock/ns" seems to resolve the issue...

Thanks for the detailed report :) seems related to #19, working on it.

Just finished installing Baikal, gotta say they got their act together :) really painless install. I've made it to handleCardDavTestAddressbookHomeset() but fail here, the problem seems to be that Baikal...

Bleh..... Turns out that Baikal does the same silly thing as OwnCloud and only persists a static list of WebDAV properties and thus breaks spec. The database structure Baikal uses...

Hey @bungabunga thanks for the report. From the research provided by @phryneas and some I've done on my own it seems like this isn't necessarily a bug in the Flock...

hello @igoralmeida, thanks for the reminder about the wiki, I wasn't aware I had it enabled for this project. I'll add the wiki documentation to my TODO list but can...