Hi list,
I noticed a strange behavior of CalDavZap :
CalDavZap is configured with cross-domain enabled. If the certificate of the Caldav server (i.e. DAViCal) is not trusted, CalDavZap fails to connect and raises a 404 error in the console :
OPTIONS https://davical.mydomain.example/caldav.php/ [0ms] "Info: [globalNetworkCheckSettings: 'https://davical.mydomain.example/caldav.php/'] crossDomain set to: 'true'" "Error: [netCheckAndCreateConfiguration: 'https://davical.mydomain.example/caldav.php/'] code: '404'"
Though I didn't try, the same behavior probably exists in CardDavZap.
I think that announcing "404" doesn't really help about the actual issue which is not a non-existency but a certificate problem. What not consider modifying this error message?
Regards, Julien
Hi Julien,
in JavaScript there is no way to detect invalid certificate errors. Each browser use own custom error code (usually 0) for this situation.
JM
On Sep 2, 2013, at 1:27 PM, Julien Métairie ruliane@ruliane.net wrote:
Hi list,
I noticed a strange behavior of CalDavZap :
CalDavZap is configured with cross-domain enabled. If the certificate of the Caldav server (i.e. DAViCal) is not trusted, CalDavZap fails to connect and raises a 404 error in the console :
OPTIONS https://davical.mydomain.example/caldav.php/ [0ms] "Info: [globalNetworkCheckSettings: 'https://davical.mydomain.example/caldav.php/'] crossDomain set to: 'true'" "Error: [netCheckAndCreateConfiguration: 'https://davical.mydomain.example/caldav.php/'] code: '404'"
Though I didn't try, the same behavior probably exists in CardDavZap.
I think that announcing "404" doesn't really help about the actual issue which is not a non-existency but a certificate problem. What not consider modifying this error message?
Regards, Julien