It works with a WebBrowser because it uses a cookie from the first request when making the second request, which is exactly what I suggested you do in my previous post. It is absolutely the wrong option to use a WebBrowser. It is a UI element and you don;t want the user to interface with this operation, obviously. The WebRequest class exists so that you can do this sort of thing without user interaction. If you don't know how to do something then you learn. Have you researched using a WebRequest? If you search properly then I know you'll find information because, as I said, I've seen it before myself. The first order of business should be to read the documentation for the WebRequest, HttpWebRequest and HttpWebResponse classes.