Bankai's forced TLS makes developing for Beaker Browser difficult

[s3ththompson]

Choose one: 🙋 feature request

Bankai's forced TLS means that it's difficult/impossible to develop inside Beaker Browser right now. Beaker doesn't yet have a way to navigate around an invalid/self-signed TLS warning: beakerbrowser/beaker#419

Is it possible to make HTTP an option? Or at least make it an option to disable HTTP->HTTPS redirection?

[santiagogil]

Hi @s3ththompson I found that starting beaker with --ignore-certificate-errorsexit flag does the trick.

[austinfrey]

@santiagogil this is gold!!

[blahah]

just to be clear the flag is --ignore-certificate-errors