Dave E

I have written an application that reads third party web pages. If I am
using HTTP everything works fine.



I create an AxSHDocVw.AxWebBrowser object and then Navigate2 to the page. I
then populate some form fields, browse to the appropriate button on the page
and then call it's click method. This works just fine using HTTP. However,
one of the web pages changed to HTTPS (actually 2 of them have). Now, the
click does not throw an exception, however it does not do anything either. I
also display the web page so I can see that the form fields get populated
successfully. If I then click the button manually in the
AxSHDocVw.AxWebBrowser windows it works fine. But the click event does not
seem to do anything. Again, this works just fine with HTTP.



Any suggestions? I am using C# and have tried both Visual Studio 2003 (have
to use it for the .net version) and Visual Studio 2005 SP1. I have used both
IE6 and IE7 as the browser on the computer as well.



Thanks,

--
Dave E

Nicholas Paldino [.NET/C# MVP]

Dave,

It sounds like a security issue to me. Since it is an HTTPS site, IE
might think that script access should be disabled to some degree (it might
see external manipulation of the DOM as a Cross Site Scripting attack).


--
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com

"Dave E" <DaveE@discussions.microsoft.com> wrote in message
news:334709CF-2FB0-4E86-88DB-64D24042705B@microsoft.com...
>I have written an application that reads third party web pages. If I am
> using HTTP everything works fine.
>
>
>
> I create an AxSHDocVw.AxWebBrowser object and then Navigate2 to the page.
> I
> then populate some form fields, browse to the appropriate button on the
> page
> and then call it's click method. This works just fine using HTTP.
> However,
> one of the web pages changed to HTTPS (actually 2 of them have). Now, the
> click does not throw an exception, however it does not do anything either.
> I
> also display the web page so I can see that the form fields get populated
> successfully. If I then click the button manually in the
> AxSHDocVw.AxWebBrowser windows it works fine. But the click event does
> not
> seem to do anything. Again, this works just fine with HTTP.
>
>
>
> Any suggestions? I am using C# and have tried both Visual Studio 2003
> (have
> to use it for the .net version) and Visual Studio 2005 SP1. I have used
> both
> IE6 and IE7 as the browser on the computer as well.
>
>
>
> Thanks,
>
> --
> Dave E

Dave E

So am I out of luck, or is there possibly a work around? I can't seem to
find any options to set to work around it.

--
Dave E


"Nicholas Paldino [.NET/C# MVP]" wrote:

> Dave,
>
> It sounds like a security issue to me. Since it is an HTTPS site, IE
> might think that script access should be disabled to some degree (it might
> see external manipulation of the DOM as a Cross Site Scripting attack).
>
>
> --
> - Nicholas Paldino [.NET/C# MVP]
> - mvp@spam.guard.caspershouse.com
>

Nicholas Paldino [.NET/C# MVP]

Dave,

If it is indeed a security issue that is preventing the DOM model from
being changed programmatically, then yes, you are out of luck.

It sounds like you are trying to automate the browsing of some pages.
You could use the HttpWebRequest/HttpWebResponse classes to send the HTTP
requests and process the responses.


--
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com

"Dave E" <DaveE@discussions.microsoft.com> wrote in message
news:A2A22D2C-CAAA-4EFC-BCCC-F37CFB1475DD@microsoft.com...
> So am I out of luck, or is there possibly a work around? I can't seem to
> find any options to set to work around it.
>
> --
> Dave E
>
>
> "Nicholas Paldino [.NET/C# MVP]" wrote:
>
>> Dave,
>>
>> It sounds like a security issue to me. Since it is an HTTPS site, IE
>> might think that script access should be disabled to some degree (it
>> might
>> see external manipulation of the DOM as a Cross Site Scripting attack).
>>
>>
>> --
>> - Nicholas Paldino [.NET/C# MVP]
>> - mvp@spam.guard.caspershouse.com
>>
>

Dave E

Is there someone who could answer if it is an issue or not? Do I need to
open a case with MS to get a definitive answer? This is rather important for
me. Or if someone knows of a third party redistributable that performs
similarly that would be great as well.

Unfortunately because of cookies, multiple script files being loaded and
needed to run and the overall complexity of the pages, I can't really use the
httpweb classes for this. I started out using them, but I really need to be
able to execute the web pages and then perform actions on them and use IE as
an interpreter of the pages.

--
Dave E


"Nicholas Paldino [.NET/C# MVP]" wrote:

> Dave,
>
> If it is indeed a security issue that is preventing the DOM model from
> being changed programmatically, then yes, you are out of luck.
>
> It sounds like you are trying to automate the browsing of some pages.
> You could use the HttpWebRequest/HttpWebResponse classes to send the HTTP
> requests and process the responses.
>
>
> --
> - Nicholas Paldino [.NET/C# MVP]
> - mvp@spam.guard.caspershouse.com
>