I want to be able to store seperate cookies in each web browser instance...

Yet I can't find out how they are stored, I can change them on the per-document level... but that wouldn't be a good idea would it? It would change global cookies too right?

Basically I want to create some kinda cookie container (not the one used for httpwebrequest...) and assign each browser it's own container...


I've also heard about extended web browser controls and web browser controls based off the firefox engine, wheres info on these, I can't find them.

You can't do this either for example if you had created your own request and response objects then you enter form data in the webbrowser control those cookies do not persist into the browser control and if you handled the navigating before the browser did and cancelled the browser from navigating then you'd still be left with the issue of handling the form data which would then defeat the whole purpose of using the WebBrowser control to begin with!

Hi Strange_Will,
An answer is coming quite late... but it may help others. So here a way to add a cookie to the webBrowser control: (works great!)

public partial class WebBrowserControl : Form
{
private String url;

[DllImport("wininet.dll", CharSet = CharSet.Auto, SetLastError = true)]
public static extern bool InternetSetCookie(string lpszUrlName, string lbszCookieName, string lpszCookieData);

public WebBrowserControl(String path)
{
this.url = path;
InitializeComponent();

// set cookie
InternetSetCookie(url, "JSESSIONID", Globals.ThisDocument.sessionID);

// navigate
webBrowser.Navigate(url);
}
...
}

For more info, see this blog entry: http://en.gli.sh/Blog/default,month,2006-11.aspx

The problem isn't in setting cookies, its that I need each webbrowser instance to have it's own cookie container. You have to write your own httprequest/response interface for the browser. :P

You can't do this either for example if you had created your own request and response objects then you enter form data in the webbrowser control those cookies do not persist into the browser control and if you handled the navigating before the browser did and cancelled the browser from navigating then you'd still be left with the issue of handling the form data which would then defeat the whole purpose of using the WebBrowser control to begin with!

I try it ,but not succeed!

---

Focus in C# developing