Re: [Evolution] Evolution and the X-NC-CalDAV-Webcal-Caching header

On Tue, 2020-05-26 at 14:02 +0200, Robin Lee via evolution-list wrote:
Failed to connect calendar “Nextcloud : Personal”
Failed with HTTP error 404: Not Found

this will be harder to debug. You can check in the Properties of the
calendar what URL had been discovered (as advertised by the server).

You can also see what the discovery does with:

   $ WEBDAV_DEBUG=1 /usr/libexec/evolution-source-registry

Finally, you can see what the calendar does with:

   $ CALDAV_DEBUG=1 /usr/libexec/evolution-calendar-factory -w

The actual path can differ in your distribution. There's nothing to be
shared in public from those two logs, it contains a lot of private
information, some even encoded (in base64 or similar encoding), thus
unreadable on the first look. You can see from it what the server

It feels surprising to see the server returning an invalid Personal
calendar URL. Might there be double-encoding involved or something,
what would Evolution(-data-server) code decipher incorrectly? Just
check what the calendar has set (it can be copied out of the
Properties, even when it shows ellipsized), maybe it'll help to narrow

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]