Skip to content
New issue

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

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

Already on GitHub? # to your account

SSL Self signed certificate #970

Closed
vincentmorneau opened this issue Jan 19, 2016 · 1 comment
Closed

SSL Self signed certificate #970

vincentmorneau opened this issue Jan 19, 2016 · 1 comment

Comments

@vincentmorneau
Copy link

I'm having an issue with the SHA-1 certificate. This is what I'm getting (Firefox):

image

Is is possible to switch to SHA-2 when using a proxy?

This is how I launch browsersync:

browserSync.init({
            host: host,
            port: config.browsersync.port,
            notify: config.browsersync.notify,
            proxy: {
                target: apexHost + apexQueryString,
                middleware: function (req, res, next) {
                    res.setHeader('Access-Control-Allow-Origin', '*');
                    next();
                  }
            },
            serveStatic: [config.distFolder]
        });

Am I missing something?

@shakyShane
Copy link
Contributor

This is just a warning, Browsersync is a development only tool so we don't tend to worry too much about security related issues such as these...

Having said that, we will be using a better cert thanks to the PR mentioned above

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants