This is a migrated thread and some comments may be shown as answers.

UseHttpProxy screws up https in IE8

14 Answers 211 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Claus
Top achievements
Rank 1
Claus asked on 04 Jan 2012, 02:33 PM
Set UseHttpProxy=true and then do this:

ActiveBrowser.NavigateTo("https://www.tradingfloor.com/accounts");

 Depending on security settings and the SSL certificate installed, the page either doesn't load or displays a security warning in IE instead of loading the page. If you turn off UseHttpProxy, it works. The security warning can be worked around, but not when the page doesn't load at all.

This gets worse with a self-signed SSL certificate, which we use in our test environments (where we need to run the tests!). Here, the page doesn't load at all and so we can't test anything related to SSL.

The error is seem in IE8 and Latest build, 2011.2.1303. Interestingly, it works fine in FF.

Kind regards
Saxo Bank A/S

Claus Topholt

14 Answers, 1 is accepted

Sort by
0
Anthony
Telerik team
answered on 04 Jan 2012, 08:34 PM
Hello Claus,

Follow solution 2 listed in this article to register a certificate for HTTPS connection with the Telerik Http Proxy from the command line. This will eliminate the security certificate warnings.

If the page does not load at all, I'll need additional information so I can reproduce the issue locally and troubleshoot it.

All the best,
Anthony
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Claus
Top achievements
Rank 1
answered on 04 Jan 2012, 08:37 PM
I tried that step, the popup just says "Certificate already installed". Besides, which certificate should it install? There are no command-line options to select from.

I have attached our internal certificate here. It's served to the browser by a load balancer in front of the servers under test, if that makes any difference.

Kind regards
Saxo Bank A/S

Claus Topholt
0
Claus
Top achievements
Rank 1
answered on 04 Jan 2012, 08:57 PM
Here are some screenshots of the test process + Fiddler.

/ Claus
0
Claus
Top achievements
Rank 1
answered on 05 Jan 2012, 01:23 PM
And here is a trace log.

Kind regards
Saxo Bank A/S

Claus Topholt
0
Anthony
Telerik team
answered on 05 Jan 2012, 05:04 PM
Hello Claus,

It should install the DO_NOT_TRUST_FiddlerRoot certificate (see screen shot). Verify this under:

  • IE > Tools > Internet Options > Content tab > Certificates button

If multiples exist they all might not be from Telerik. Delete any existing FiddlerRoot certificates on each of the six tabs and register from the command line once again. Press the YES button on the prompt and the certificate should install correctly.

Concerning the Cannot display the webpage message: are you sure the URL is correct?

  • https://bluetradingfloor.sys.dom/login

I haven't heard of a top level domain called dom, so hopefully this issue is a simple typo.

Regards,
Anthony
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Claus
Top achievements
Rank 1
answered on 05 Jan 2012, 07:22 PM
Unfortunately there's no typo :-) The .sys.dom is the name of the bank's (internal dns) domain.

Works fine in IE8 with the HttpProxy off, does not work with it on. Also, as written in a previous comment, it works with the HttpProxy on in FF. Hard not to consider it a bug..

Kind regards
Saxo Bank A/S

Claus Topholt
0
Claus
Top achievements
Rank 1
answered on 09 Jan 2012, 10:39 AM
Any news?

Kind regards
Saxo Bank A/S

Claus Topholt
0
Anthony
Telerik team
answered on 09 Jan 2012, 06:36 PM
Hello Claus,

Do you have any proxy settings in IE that could be interfering? What are the proxy settings before and after a test run with the HttpProxy on?

Also, does this work correctly in Safari and Chrome?

All the best,
Anthony
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Claus
Top achievements
Rank 1
answered on 09 Jan 2012, 07:49 PM
It doesn't work in Chrome either. Error message shown is:

This webpage is not available
The webpage at https://bluetradingfloor.sys.dom/login might be temporarily down or it may have moved permanently to a new web address.
Error 111 (net::ERR_TUNNEL_CONNECTION_FAILED): Unknown error.

We do use a proxy script in IE and FF doesn't always use that, which could explain the difference in behavior. However, from what I can read the proxy sends traffic DIRECT to all internal hostnames, including *.sys.dom. I can't send you the proxy script on this open forum, but if you send me an email I can send it directly.

Also, if I point FF to use the same proxy configuration url as IE, FF continues to work...

Kind regards
Saxo Bank A/S

Claus Topholt

0
Anthony
Telerik team
answered on 10 Jan 2012, 07:19 PM
Hello Claus,

That information about Chrome and your proxy script confirms our suspicions that it will not work in this case. 

Firefox is the only browser where the Telerik HttpProxy doesn't inject a proxy script. You're seeing the error in the other browsers because you're using your own proxy script, and it's interfering with that of the Telerik HttpProxy. The two are competing for the same spot, essentially.

I've been informed by our developers that this is simply how it works, and there aren't any settings to change to get around it.

All the best,
Anthony
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Claus
Top achievements
Rank 1
answered on 10 Jan 2012, 09:35 PM
Hi again,

Are you sure about the conclusion? Note that as stated, we can use the HttpProxy in IE against our live tradingfloor.com website with a proper SSL certificate, with that proxy script active. We just can't use it on the internal testservers on .sys.dom which has a self-signed certificate.

I just want to be 100% sure before I write up the final conclusion that we can't use the HttpProxy at all -- one of the major features that your product has and Selenium doesn't.

I'm sorry to be blunt, but we're now down to the only advantage of using Telerik Testing Framework over Selenium is better documentation, and that's just not enough to buy any licenses.

Kind regards
Saxo Bank A/S

Claus Topholt
0
Anthony
Telerik team
answered on 11 Jan 2012, 11:02 PM
Hello Claus,

Here's a final test to try. Download and install Fiddler. Run it and select File > Capture Traffic (or press F12). Then access your internal .sys.dom site manually (outside of Test Studio / not through the Framework).

If the page does not render or traffic is not captured in Fiddler, then the Telerik HttpProxy will not work, as it injects in the same manner as Fiddler.

All the best,
Anthony
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Claus
Top achievements
Rank 1
answered on 12 Jan 2012, 10:02 AM
We use Fiddler all the time, and it works fine with https, including the https://bluetradingfloor.sys.dom example.

It does NOT work, however, if the "Decrypt HTTPS CONNECTs" option is enabled. Then the result is just like when using your HttpProxy! See attached.

I still say this is a bug.

Kind regards
Saxo Bank A/S

Claus Topholt
0
Anthony
Telerik team
answered on 13 Jan 2012, 12:45 AM
Hello Claus,

That is exactly the expected behavior I previously described. The Telerik HttpProxy is essentially using the core of Fiddler with that option enabled, so the results are the same.

That option is not configurable through the Telerik Framework. If it were and you turned it off, then automation would not function properly. So the idea of proposing this as a feature request becomes moot.

Regards,
Anthony
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Tags
General Discussions
Asked by
Claus
Top achievements
Rank 1
Answers by
Anthony
Telerik team
Claus
Top achievements
Rank 1
Share this question
or