-
July 31st, 2020, 11:42 AM
#6
Hi,
Our javascript client samples connect to the Server by using, as the protocol, the same as "document.location.protocol".
Hence, if a page is loaded via "http", it will connect to the Server via "http", whereas if it is loaded via "https" it will connect to the Server via "https".
There is no alternative to this, because, if you mix the protocols, the browser will prevent the page from reading the Server answer. Hence no working sample code can be devised in this case.
To resume, if your page is loaded via https, it can only connect to a Server via https (even though the domain can be different).
So, you have two options:
- Configure the Server to accept https requests.
In this case, you need to own a domain and to acquire certificate. You also need a license for Lighstreamer Enterprise edition. - Configure the Server to accept http requests and place a TLS/SSL offloader in the middle.
In this case, you can use Lightstreamer Community edition. Moreover, you don't need to own a domain, as long as you have access to an offloader through some cloud service (perhaps the same that hosts your pages).
You can find details on these architectures in our Clustering document.
We cannot suggest you how to proceed because we don't know what you have available.
Similar Threads
-
By rvkvino in forum General
Replies: 3
Last Post: May 21st, 2018, 09:11 AM
-
By rvkvino in forum General
Replies: 1
Last Post: April 24th, 2018, 10:29 AM
-
By jkrohn in forum Client SDKs
Replies: 1
Last Post: December 2nd, 2008, 10:46 AM
-
By veloearl in forum General
Replies: 1
Last Post: February 22nd, 2008, 09:23 AM
-
By Waddy in forum General
Replies: 2
Last Post: March 16th, 2007, 06:06 AM
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 11:37 PM.
Bookmarks