>My working hypothesis is that Danny's server only has Basic Auth in >place for the first outer document presented to the user, while my >server has Basic Auth in place for every document on the server.
After exploring what's going on, I think this is likely true. I believe that the server is using basic authentication to validate the user and then set a session cookie. Once the cookie is set the basic authentication is no longer required. It's a strange app. So perhaps the authentication part of the goto method does not apply recursively to the elements on the page, which means it not very useful at all. One thing I started to pursue is to find an OLE interface to set the authentication internally as if the user had already entered it. I see that even when I tell IE to save the password, it still pops up the login dialog. So it's not good enough to get it to save the password in that way - IE needs to have the password set in its memory as if the user has entered it - as you suggested. Maybe doing the GUI automation isn't such a bad solution. But let's see if IE gives us this password setting mechanism before we give up. -Danny _______________________________________________ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
