The problem is that it'll be separate cookies (wwHTTP and IE). I have a work-around going right that seems to handle it well. Thanks for the help guys.

paul


>>So if I use West Wind's HTTP client stuff, Mabry or this HTTP wizard I'm pretty darn sure the cookie isn't going to work (although I do need to test it - which is impossible because we can't duplicate their network setup right now). So that's why I asked for a control that works exactly like the Webbroswer control except allows for more client side control.
>
>wwHTTP supports cookies transparently, so that would be covered, but the rest of it you'd still need to automate (as you do with IE) by parsing the content and figuring out what to do next.