Skip to content
This repository has been archived by the owner on Jul 6, 2021. It is now read-only.

Allow ws:// versus wss:// protocol to be configurable #67

Open
alexdixon opened this issue Jul 23, 2015 · 3 comments
Open

Allow ws:// versus wss:// protocol to be configurable #67

alexdixon opened this issue Jul 23, 2015 · 3 comments

Comments

@alexdixon
Copy link

The bit I got stuck on trying to get ssl working for our Rails/nginx setup was that the protocol is hard-coded to ws:// in livereload.js. Changing that to wss allowed me to set up the right ssl proxy in nginx to guard.

@mcmillion
Copy link

Ran into this issue trying to get this set up on a new project that's using https. This apparently works in the current livereload project. This project's livereload.js hasn't been updated in 3 years.

@richardonrails
Copy link

richardonrails commented Jan 12, 2019

@mcmillion Where is the "current" livereload project? The README here points to https://github.com/onesupercoder/rack-livereload but it's hardcoded to ws:// there too:

https://github.com/onesupercoder/rack-livereload/blob/c4262f119428870bda5f65f379252c8216499df6/js/livereload.js#L141

@richardonrails
Copy link

Also related: guard/guard-livereload#143

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

3 participants