Skip to content
This repository has been archived by the owner on Apr 15, 2019. It is now read-only.

Enabling beacon and bandwidth tests using HTTPS #46

Open
casutherland opened this issue Sep 14, 2012 · 1 comment
Open

Enabling beacon and bandwidth tests using HTTPS #46

casutherland opened this issue Sep 14, 2012 · 1 comment

Comments

@casutherland
Copy link

You said, in follow-up to Issue #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
Copy link
Contributor

Let's move this discussion over to the https://github.com/lognormal/boomerang/ issues page since no one can commit to the yahoo repository.

bluesmoon added a commit to bluesmoon/boomerang that referenced this issue Feb 6, 2015
Changed BW calculation PNG images to be incompressible

Also closes issue YahooArchive#46
bluesmoon added a commit to bluesmoon/boomerang that referenced this issue Mar 21, 2016
Changed BW calculation PNG images to be incompressible

Also closes issue YahooArchive#46
bluesmoon pushed a commit to bluesmoon/boomerang that referenced this issue Mar 8, 2017
…ookies-fix

Test if a cookie can be set to determine which branch to test, as PhantomJS can set cookies on localhost.

Reviewed by: @cvazac
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants