Summary: | dav groupware resource always asks about logging in on startup | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Silver Salonen <silver.salonen> |
Component: | DAV Resource | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | greg, smartins |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Silver Salonen
2012-03-09 14:57:04 UTC
Hi, Which KDE / KDE PIM versions are you using? Cheers, Grégory Started using DAV resource in KDE 4.8.0, currently using 4.8.1. This means that the remote end answers with something else than a 401 (maybe a 3XX response code) that triggers this alert. If you try to connect to the address you configured with a web browser are you redirected to another page? If so, try to configured the URL at which you are. Cheers, Grégory Well, the eGroupware resource is configured with URL ".../groupdav.php/", but its calendar is under ".../groupdav.php/calendar/", so I guess some redirection takes place indeed? I now tried changing protocol (CalDAV and CardDAV) URLs of the resource. When I set CalDAV URL to ".../groupdav.php/calendar/", I lost the TODO-list (which is under ".../groupdav.php/infolog/"), but the warning remained. So I don't know the one and only answer to your question :) For egw /groupdav.php/ is the standard location. I was more thinking about a redirection from, for example, https://egw.domain.com/groupdav.php/ to https://domain.com/egw/groupdav.php/. Ah, I see. But no, there's no redirection in that part. I've discovered that actually KOrganizer opens the calendar before I manage to hit "yes". I did not realize it before, because it takes about 5 seconds for the calendar to open, so I had already clicked "yes" when the calendar opened. Anyway, maybe that question is not asked in order to decide whether to open the calendar, but for something else? This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |