| Summary | Lighttpd rpc publishing doesn't work |
| Queue | Kronolith |
| Queue Version | 2.2-RC3 |
| Type | Bug |
| State | Not A Bug |
| Priority | 2. Medium |
| Owners | |
| Requester | horde (at) hauke-m (dot) de |
| Created | 05/16/2008 (6257 days ago) |
| Due | |
| Updated | 05/16/2008 (6257 days ago) |
| Assigned | 05/16/2008 (6257 days ago) |
| Resolved | 05/16/2008 (6257 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
system. There is really no need to post duplicate info,
simultaneously, to both.
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
State ⇒ Feedback
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Lighttpd rpc publishing doesn't work
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
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