Hey there,
Now that Quantum is out I’m scratching our old Firefox add on in favor of a web extension, and as a starting point we’re porting over our Chrome extension. Our current Chrome extension behaves as a self contained client side app, down to login creating a session cookie (and some other values) which we store.
When I attempt to authenticate with the extension in firefox, the set-cookie headers are ignored and the next request the user makes is considered unauthenticated—is that the expected behavior, or are there some headers that I have configured incorrectly that’s causing those set-cookie responses to be ignored?
My thought for a workaround would be to listen to the webrequests that the extension makes and use the cookies API to set the cookies that we hear, but I wanted to double check to make sure I’m not missing something since the default web-like behavior of saving the set-cookie values would help a lot in making our firefox extension behave like our chrome extension.