-
April 13th, 2007, 05:14 PM
#3
hmmm... This is going to make things interesting then. Our site is currently set up so that it is in the following format: https://site1.system.com for the main web applications and https://site2.system.com for the lightstreamer portion. Where the system.com portion is the same for both sites. The www.* part is not applicable in our situation. Is this still a invalid deployment scenario?
If it is no longer a problem, would my set up be simular to this:
LSHost = "site2.system.com"
Domain = "system.com"
If it is still a problem maybe you can give me some more ideas on how to get around it. The primary issue for us is that our firewalls only allow port 443 through them. Once traffic makes it through the firewall it is then authorized using windows "Basic" authorization scheme. (name and password required, no anonymous access allowed - issue #1) On the backside of the firewall our https://site1.system.com maps to webserver:80 (IIS - no longer ssl encrypted), and https://site2.system.com maps to webserver:8008 (Lightstreamer - no longer ssl encrypted). Unfortunently we have no way to allow any ports other than 443 thorough the system.
With this constraint, is there a better way to config this? All ideas are appreaciated!
Thanks!
Similar Threads
-
By Mone in forum Client SDKs
Replies: 1
Last Post: July 10th, 2012, 06:06 PM
-
By RichPratt in forum Adapter SDKs
Replies: 7
Last Post: June 7th, 2010, 09:38 AM
-
By hofmanna in forum Client SDKs
Replies: 3
Last Post: February 18th, 2010, 11:14 PM
-
By jondcruz in forum General
Replies: 1
Last Post: September 18th, 2009, 09:13 AM
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 03:09 AM.
Bookmarks