Enabling beacon and bandwidth tests using HTTPS

[bluesmoon]

Mirroring YahooArchive#46 by @qcu

You said, in follow-up to Issue YahooArchive#18: "yeah, my guess is that no one really runs it over HTTPS. There was a similar bug someone emailed me about but regarding their own plugin."

@bluesmoon, I do actually need to run boomerang beacon over HTTPS, especially including bandwidth/latency tests. Also, the image GETs really need to run over HTTPS as well for my test scenario.

Before I look into this further, is this something that just needs some attention and testing, or are there significant issues blocking this (i.e., "SSL stuff will mess up b/w calculations").

[bluesmoon]

Establishing an SSL connection takes time, which could skew the bandwidth down, so it may not be what you want.

Now that said, if all your traffic is sent over SSL, then running the test over SSL probably gets you what you want anyway, ie, the effective network throughput that your users see during the normal browsing session.

[arajwade]

If we comment the code block in Bandwidth plugin that skips bandwidth tests on https, will the bandwidth plugin work fine over https as mentioned by you above?

Wanted to double check with you that there will be no issues with this approach.

Can you please comment on this?

Thx
--- Abhijit Rajwade

[bluesmoon]

yes, that's correct

[terraboops]

I would like to make a feature to toggle this block of code via configuration parameter.

Would you accept that pull request if I made it?

[bluesmoon]

I would indeed.

[terraboops]

I've forked off of bluesmoon/boomerang and I will submit my pull request to that repo... Let me know if this is incorrect.

[bluesmoon]

yep, bluesmoon/boomerang is correct.

[andreas-marschke]

Since this issue has been resolved and code has been merged can we close this?

[bluesmoon]

Yeah, for some reason I thought github automatically closes pull requests when code has been merged.