Thank you for the responses. The easy way, i think: If the caldav server have public url. You can open browser. Visit the url. Accept certificate. And caldav ok.
But. Why browsers always is so alarming with autosigned certificates? In desktop, mobile devices.... is impossible to create a self-signed usable service. It's a reflection only. sorry. Thanks. 2014-02-06 Alexandre Lissy <[email protected]>: > Le 06/02/2014 13:30, Mossroy a écrit : > > I faced the same issue. > > As a workaround, it's possible to install your own certificates on your > > Firefox OS device. > > I documented this a while back there: > http://wiki.mozfr.org/Adding_CA_to_FirefoxOS > > > > > There has been a discussion about that earlier on this same > > mailing-list. See > > https://groups.google.com/d/msg/mozilla.dev.b2g/vAImRu4r3n0/fWbCiYZ2lxEJ > > > > > > Le 06/02/2014 05:06, jbc a écrit : > >> Hello, when i fill caldav, username, pass and https url caldav, with > >> autosigned SSL. > >> Caldav, error. > >> Why always browsers and apps scares with SSL autosigned or fails? > >> I have pay to company of certificates NSA for to can a service cipher > with > >> SSL and browsers and apps doesn't scare? > >> > >> Thank you. > >> > > > > _______________________________________________ > > dev-b2g mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/dev-b2g > > > > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
