Migration from 1.1.3 to 1.1.7 Apache configuration scheme trouble
Dear community,
Working on Debian Jessie (I know I'm late), I've updated to last version of davical. I wanted to use the new apache configuration but I want to share here troubles and questions about it.
My clients are: Ligthning, iOS, OS X
The trouble has been observed on Lightning but maybe other clients are also concerned.
Main question: Is it possible to juste change apache configuration having new and old URL leading to the same calendar?
I mean my lightning calendar were set with https://davical.example.org/caldav.php/jhon.dow@example.org/calendar/
. I've done the job for it to resolve to the right new URL. But in lightning, I observed really strange requests like:
-
GET /caldav.php/jhon.dow@example.org/calendar/alendar/...
(don't ask me why) GET /caldav.php/jhon.dow@example.org/calendar/calendar/...
Those lead to 405 status errors.
Even worse, creating a new calendar in lightning using new URL ie. https://davical.example.org/jhon.dow@example.org/calendar/
, I observed:
GET /jhon.dow@example.org/calendar/jhon.dow@example.org/calendar/...
I've found this old Lightning bug: https://bugzilla-dev.allizom.org/show_bug.cgi?id=647812 that is maybe still present. But if I set my apache to rewrite correctly those wrong URLs from lightning then I got 412 status error, as if ETAG depends on URL scheme (it's maybe the case, I have not read the caldav spec).
By the way, looking at requests and answers in the log, I've seen that href
is often present. Looks like client and server are communicating together, leading Lightning to those wrong URL. Using [PT] in apache configuration file, makes Lightning thinks it talks to https://davical.example.org/caldav.php/jhon.dow@example.org/calendar/
whereas server sees https://davical.example.org/davical/caldav.php/jhon.dow@example.org/calendar/
from rewrite.
Any clue on what is happening? Is it even possible to have 2 calendars pointing to the same collection using 2 different URL schemes?
Best regards,