On Tue, Jul 10, 2007 at 02:40:53PM -0700, Dave Hayden wrote: > 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: ... > Seems to work if I change that to ret == 1. Thanks!
Doh! Thanks for trying it out. > 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. Have they actually fixed the bug, or are they going to ? It is cheap and harmless to work around the problem in neon, buf if it's a custom server and they'll fix it soon it's not worth it. Regards, joe _______________________________________________ neon mailing list [email protected] http://mailman.webdav.org/mailman/listinfo/neon
