Multiple set-cookies directives

Question

Hi All- I'm testing against an http server that sends multiple set-cookies directives (there are 4 cookies total). As far as I can tell, it is legit HTTP to either send a single set-cookie directive with multiple cookies in it, or multiple set-cookies directives. I am getting erratic behavior. Using the wtk emulator, i am able to receive and process multiple set-cookies directives. Using some phones it works, on others it doesn't. I am trying to create a unit test for my code, and I am unable to figure out how to set up the classpath the same way the emulator does to work with multiple set-cookies directives.
I searched the jars in the wtk22 directory, and it appears that wtklib/emptyapi.zip, wtklib/gcf-op.jar, lib/midpapi10.jar and lib/midpapi20.jar all contain the HttpConnection class. I am guessing that the emulator is picking up a different implementation than my unit test or the phones that don't work? Has anyone encountered and solved this problem before? Is there a way at runtime to determine from which jar a class was loaded?
thanks,
Bleu

Answer 1

I have a very similar authentication flow in my app.  Using native calls (HttpClient) I am able to retrieve the authentication token, and can easily set a cookie with that token, and use the cookie with subsequent
native calls via HttpClient.
I believe that what you are asking for is the ability to add that cookie (with the token you got natively) into the webbrowser control's cookie store
BEFORE trying to load your dashboard page.  You want your webbrowser control's request for the dashboard page to provide the cookie so that the user doesn't have to log
in again, and only one webbrowser request is made.  Is this correct? 
Sadly, I do not think this is possible.  The other answers describe how to add a cookie to a webbrowser control's page after that page has been loaded.  This is adding the cookie to the "document" within the browser control, not
into the webbrowser control's store.  These approaches will not allow you to add the cookie into the webbrowser control's store, ahead of time, so that it will be sent when you first request the page. 
If I am correct about what you are asking for (I want this too!) it is not supported on Windows Phone as you cannot write directly to the webbrowser control's cookie store.  You can read it, but not write to it.  It's sad as this particular
authentication flow is very common, and easy to achieve on both iOS and Android... just not on Windows Phone.
To get around this in my app, I perform my native authentication (HttpClient) and then authenticate
again within the webbrowser control itself.  Basically, load the login page into the browser, then submit the login form via eval of JavaScript, and when that finishes loading (valid
response), load the actual target page.  This is a fragile and inefficient hack, but it seems to work. 
Hope this helps...