[kronolith] Lighttpd rpc publishing doesn't work

[Hauke Mehrtens]

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

--
Hauke Mehrtens

Hauke Mehrtens wrote:
> Hi
> 
> 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
> 
> Is there a bugfix for this problem? Is there an option to set horde and
> kronolith to debug mode to get more information on this issue?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 890 bytes
Desc: OpenPGP digital signature
Url : http://lists.horde.org/archives/kronolith/attachments/20080516/6141093f/attachment.bin