Development

EWS

Mozilla

Implementation notes

11:45:55 < corecode> Fallen: any idea how i can open multiple connections to a given URL with different authentication credentials?
11:47:15 < Fallen> corecode: see bug 247486. The problem is, if the server sends the same realm for a given URL, then the mozilla backend code will re-use the auth credentials
11:47:17 < firebot> Fallen: Bug https://bugzilla.mozilla.org/show_bug.cgi?id=247486 maj, —, —–, nobody, NEW, can’t load several calendars with different passwords on same server/realm
11:47:33 < corecode> yea it does, how should it send a different realm
11:52:57 < corecode> Fallen: i'm not sure if it is the same
11:53:15 < corecode> Fallen: i don’t use the http authentication dialog, but run the dialog on my own
11:53:43 < Fallen> corecode: shouldn’t you then be able to decide on your own too?
11:53:56 < corecode> i am passing the authentication
11:54:02 < corecode> but it seems it is not honored
12:30:13 < Fallen> corecode: try implementing nsIAuthPrompt2 too
12:33:16 < Fallen> and for the POST 302 redirect, implement nsIChannelEventSink’s onChannelRedirect()

12:34:10 < corecode> what’s the policy for prompting the user for a password?
12:34:26 < corecode> or rather, when would you ask again
12:34:32 < corecode> after the user presses cancel
12:35:18 < Fallen> see bug 441992 for example :)
12:35:21 < firebot> Fallen: Bug https://bugzilla.mozilla.org/show_bug.cgi?id=441992 nor, —, —–, nobody, NEW, caldav calendar isn’t switched off after canceling the login dialog
12:35:30 < Fallen> the idea is that if the user cancels the dialog, the calendar is set to disabled mode
12:35:48 < Fallen> which means the user is asked again when he enables the calendar
12:58:50 < corecode> does the calendar have to do that by itself?
13:32:02 < Fallen> corecode: hm not sure, I think so
13:32:55 < Fallen> corecode: gdata does it, see calGoogleCalendar.js, line 187

Hosting

Upcoming at AMO