Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bankai's forced TLS makes developing for Beaker Browser difficult #506

Open
s3ththompson opened this issue Jul 13, 2018 · 3 comments
Open

Bankai's forced TLS makes developing for Beaker Browser difficult #506

s3ththompson opened this issue Jul 13, 2018 · 3 comments

Comments

@s3ththompson
Copy link
Member

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
Copy link

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

@austinfrey
Copy link

@santiagogil this is gold!!

@blahah
Copy link

blahah commented May 16, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@blahah @s3ththompson @santiagogil @austinfrey