Fri, 10 Apr 2026 19:28:36 +0000 https://bugs.horde.org/ticket/6713 Lighttpd rpc publishing doesn't work I am using Horde Groupware 1.1-RC3 and Lighting 0.7 as calendar client. Getting the calendar with Lighting is no problem, but I can't publish anything. I have set up a testing environment on my desktop with lighttpd and it doesn't work too. Now I have tested the same application with Apache2 with the same php.ini and publishing works fine. Switching back to lighttpd I get the following error message from Lighting as always: Publishing the calendar file failed Status code: 501: Not Implemented Fri, 16 May 2008 14:13:07 +0000 https://bugs.horde.org/ticket/6713#t45310 Maybe a PATH_INFO problem? Fri, 16 May 2008 15:51:52 +0000 https://bugs.horde.org/ticket/6713#t45314 When Lighting talks to Lighttpd it sends a Content-Length and a Content-Type attribute to the webserver in the http put request. The HTTP_CONTENT_LENGTH is not supported by the pear WebDav implementation so it sends back an "501 not implemented" http status for everything it doesn't know. After changing ./pear/HTTP/WebDAV/Server.php to not ending with "The service does not support" when it finds the HTTP_CONTENT_LENGTH attribute I am able to publish some entries to the calendar with Lighting and lighttpd as webserver. With Apache 2.2 as webserver Lighting doesn't ad the Content-Length and Content-Type attribute to the http request, but I don't know why. In the newest WebDav Server.php out of the cvs the problem is fixed: http://cvs.php.net/viewvc.cgi/pear/HTTP_WebDAV_Server/Server.php?view=markup Fri, 16 May 2008 15:59:27 +0000 https://bugs.horde.org/ticket/6713#t45315 Thanks for the info, but also: please pick either the list or the bug system. There is really no need to post duplicate info, simultaneously, to both. Fri, 16 May 2008 15:59:59 +0000 https://bugs.horde.org/ticket/6713#t45316