The issue is about the use of nsICookieSettings. If you create a channel without an associated document, by default, we create a new nsICookieSettings which blocks cookies. The idea behind this decision is that chrome code, by default should not send/receive cookies. A good description of what nsICookieSettings is can be found here: https://searchfox.org/mozilla-central/rev/7ed8e2d3d1d7a1464ba42763a33fd2e60efcaedc/netwerk/cookie/CookieSettings.h#20
About your particular use-case, there are 3 ways to proceed: 1. create and set a cookieSettings object in the loadInfo of your channel before calling asyncOpen()/open(). - hard to do because CookieSettings cannot be created from JS yet. 2. create a channel from a document/worker. - recommended! 3. disable the cookieSettings block: see pref network.cookieSettings.unblocked_for_testing - you don't want this! We can move this discussion on slack/bugzilla/irc. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
