-
-
Notifications
You must be signed in to change notification settings - Fork 596
SSL and LiveQuery? #271
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.
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
Comments
I've fixed this client-side for the meantime by replacing with the following at line 3653 in parse-latest.js if (!liveQueryServerURL) {
var tempServerURL = _CoreManager2['default'].get('SERVER_URL');
var protocol = 'ws://';
if (tempServerURL.indexOf('https') === 0) {
protocol = 'wss://'
}
var host = tempServerURL.replace(/^https?:\/\//, '');
liveQueryServerURL = protocol + host;
_CoreManager2['default'].set('LIVEQUERY_SERVER_URL', liveQueryServerURL);
} |
Want to submit a PR for this? |
Merged
PR Submitted! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've secured my app with SSL and everything is working as expected, aside from LiveQueries. I'm accessing my parse-server from an SSL webpage as well and receive the following error from the web console:
https://example.com/ was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://example.com/parse'. This request has been blocked; this endpoint must be available over WSS
So I assume this is a simple matter of LiveQueries not creating a secure WebSocket connection and providing the correct protocol. Is this something that is being worked on, or how can I ensure I have access to the live query protocol behind ssl.
Thanks!
The text was updated successfully, but these errors were encountered: