|
|
On Jul 10, 2007, at 1:07 AM, Joe Orton wrote:
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?
No to both of those questions - but eating the blank lines in
read_status_line() should be safe; can you try this:
[...]
+ do {
+ ret = ne_sock_readline(req->session->socket, buffer,
sizeof req->respbuf);
+ if (ret <= 0) {
+ int aret = aborted(req, _("Could not read status
line"), ret);
+ return RETRY_RET(retry, ret, aret);
+ }
+ } while (req->session->persisted && ret == 2 && buffer[0] ==
'\n');
+
Seems to work if I change that to ret == 1. Thanks!
They wrote back to say that they're currently not planning on adding
WebDAV to their services, but didn't mention whether they're using an
open source server here. My guess is it's an in-house bug, nothing
you'd ever run into elsewhere.
-D
_______________________________________________
neon mailing list
neon@xxxxxxxxxx
http://mailman.webdav.org/mailman/listinfo/neon
|
|