Am 23.07.10 20:46, schrieb Doug McNutt:
> It doesn't look like a problem with the curl tool. It attempted an
> HTTP PUT request and properly told the server that the file length
> was zero. Libcurl has its own list
> <http://cool.haxx.se/mailman/listinfo/curl-library>. If mod_webdav
> uses the curl library that would be a place to look.
>
> But your curl tool call clearly went to port 80 and was processed by
> WebDAV probably in the mod_webdav addition. That was where the 204
> rejection came from. Apache, or the mod, refused to complete, or even
> start processing with a continue reply, the request because no file
> content (zero length) was going to be sent. It sounds like a bug to
> me though reasonable folks might disagree.
That is probably true. There is absolutely nothing in Apache's logs
because Apache did not even start to process the request.
If it is a "bug" within mod_webdav, where can I ask for help about this
mod? I don't think there is a seperate webpage or mailing list dealing
with this mod?!?
> The Server: HTTP header doesn't mention mod_webdav. Are we sure it's
I'm quite sure since (this might sound stupid) I can "mount" the
directory with r/w access on the server with my Mac's finder ("Connect
to server...").
> there? Those things are out of my expertise. Could you be getting to
> a different instance of Apache?
Unfortunately not. Well, ok, I could try to configure WebDAV on my Mac.
> Does mod-webdav put out any log files? I'm out of my chosen field
> there. Can you put a couple of nulls in the "empty file" without
> messing up your Zotero interface? date > empty ?
Dan Stillman was so kind to change Zotero a bit. The "lastsync" file now
contains a single space. I'll try this tomorrow first. I'll tell you
what happend....
Regards,
Thorsten
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|