When I do a DELETE on box.net's webdav server, the response has an
extra \n after the blank end-of-headers line, even though it's a 204
No Content and shouldn't have a body. It's a keep-alive connection,
so the next request reads the buffered \n and throws a "couldn't
parse response" error.
I've asked them for info to try and track down the bug on the server
side (headers aren't identifying what's doing the DAV), but I'm
looking at workarounds for the client. Would it be safe/sane to just
clear the read buffer when sending out a request? If so, is
ne_begin_request() a bottleneck for all requests?
Thanks!
-Dave
_______________________________________________
neon mailing list
[email protected]
http://mailman.webdav.org/mailman/listinfo/neon
