
andrew at morphoss
Feb 14, 2012, 12:13 PM
Post #5 of 5
(294 views)
Permalink
|
|
Re: problem with iOS-clients: 'server URL'-setting disappears silently
[In reply to]
|
|
On Tue, 2012-02-14 at 10:14 +0100, Vincent Van Houtte wrote: > Hi Andrew, > > Thank you for your continuing high level of unpaid support. Writing the > word 'unpaid' made me check again if there was no way to contribute > financially to the project, but no option is listed (so far)... I'm happy to accept contributions any way you want to send them :-) There is no trust or foundation framework behind DAViCal, though I have considered applying to SPI for that, so at present contributing financially to the project really means "paying Andrew something so he doesn't get so distracted by work". [1] I operate a company "Morphoss Ltd" which is basically $ME which I can also use if you want a contract for support services, or an invoice for some donation. > > I've heard some other reports of this happening, and I believe that the > > Apple software attempts to rediscover the server in some communication > > error situations. > > > > Other than filing bugs with Apple I don't know what might resolve the > > issue. Possibly setting up SRV records for your domain *might* help. > > I will look into those. I remember seeing them on the wiki, but I'm > quite conservative in mucking around with DAViCal... SRV records are something which happens entirely outside of your DAViCal installation - hopefully that will make it easier to take the step. It's not always possible, however, depending on how you administer the DNS for your organisation. > > It would be good to be able to characterise the "some communication > > error situations" more accurately. Perhaps it is LDAP lookup failures > > causing authentication failures - that seems to ring a bell, and maybe > > DAViCal could return an error other than '401' in that case. > > I just wanted to let you know that server is not using LDAP auth (^^ > conservative-thingie...), so that should not be the problem. > > It is also very difficult to tell exactly when the problem occurs, > because it doesn't throw an error and is noticed some (indefinite) time > later. Yeah, I understand the issues. Also it's normal for the Apple clients to get a 401 when they send a request because they leave off the username / password and then re-request with those details in response to the 401, making it a lot harder. Regards, Andrew. [1] Or Real Life, such as my wife's cancer operation happening tomorrow... -- ------------------------------------------------------------------------ andrew (AT) morphoss (DOT) com +64(272)DEBIAN You can observe a lot just by watching. -- Yogi Berra ------------------------------------------------------------------------
|