Xarigami

project tracker

Xarigami Core [key: xgami]

All trackers
Summary
Issue List
Road Map
Changelog

Issue xgami-000847

Issue summary Details
Project:
Xarigami Core
Key:
xgami-000847
Type:
Improvement
Reporter:
Lakys
Priority:
Normal
Severity:
Minor
Status:
Closed
Resolution:
Implemented
Owner:
Lakys
Due:
- xarigami cumulus 1.4.0
Milestone:
None

https detection

Reported:  May 8, 2011 09:40 AM    Updated: May 8, 2011 09:49 AM by

Closed: May 8, 2011 09:49 AM    by Lakys

Version affected: - xarigami cumulus 1.3.5

In some cases, the detection of https / secure server is not working.

There is no real way to be sure that the content is using an SSL encryption. https seems to be the most appropriate but would fail with some server if the environment var is not specified.

More than all, the SSL encryption could be done by device distinct from the web server such as a firewall, a load balancer.

So while keeping and fixing the old way to detect https (so it should continue to work), we add a custom SSL TCP port to specify (default is 443). The admin in Site Base / Session and security can then specify on which port the SSL connection is expected. Then if any connection happens on that port, it will be identified as "secure".

To make it working, you also need to have the secure server check.

Actions
Did you know relative section Lakys May 8, 2011 09:48 AM
Resolved: https detection Lakys May 8, 2011 09:49 AM

done

#

Closed: https detection Lakys May 8, 2011 09:49 AM

Issue closed by Lakys

#