Are you sure that your local network doesn't have a transparent proxy that is being run by the security team? If so it's going to screw with performance but you can get around it by installing the appropriate certificates on your test agents.

(11-14-2014 05:33 AM)pmeenan Wrote: Are you sure that your local network doesn't have a transparent proxy that is being run by the security team? If so it's going to screw with performance but you can get around it by installing the appropriate certificates on your test agents.

What you are describing is what you will usually see if the server is presenting an invalid SSL certificate and it's not a config difference with the test agents and the public ones. Does it affect all sites you test or just your site?

If you check the box to ignore certificate errors when running the test does it work?

The most common reasons I've seen something like that are:

1 - If it is only your site having issues, accessing your site from your internal LAN may be going directly to a server, a staging server or some server that is not the same endpoint that external traffic goes through and it isn't configured with the production certs.

2 - There is a transparent proxy on the LAN->Internet egress that the security team uses to filter web access and for SSL traffic it uses self-signed certs and relies on the client machines to have the root cert installed (common in large corporations and schools).

It could be something else but those are by far the most common reasons it happens.

"Visual Comparison" is just a shortcut for creating a comparison. You can create comparisons of any arbitrary tests:

1 - Run each test individually with video capture enabled (and any other settings)
2 - Go to test history
3 - Select the tests you want to compare
4 - Hit the compare button

There isn't any setting to permanently disable cert warnings (feel free to file an issue on github). That said, it's not reallly the right way to fix it. Something in your path is still serving bogus certificates.