Kablink Component
Hi, a great software, after playing around we fall in love with it. Our question is when we installed 2.0 Beta 1 last week all emails notification sent to team members with a hyperlink of https://team.xxx.com, however after upgraded to 2.0 Beat 2 all the emails changed to http://xxx.com. System is installed with port 81 and SSL at port 444, as port 81 is blocked by our firewall, nobody can login teaming by directly clicking the hyperlink in mail.
Our setup: 1. Windows 2003 Ent. server / Win 2000 datacenter 2. http: at port 81 and SSL at port 444 3. All other settings are default. 4. Client : Firefox / IE When login (2.0 Beta 1) with https://team.xxx.com, the email notification automatically emailed out to user with https://team.xxx.com, after updated to 2.0 Beta 2, email always shows http://team.xxx.com:81 no matter we login with https://team.xxx.com:444 or http://team.xxx.81(test by temporarily open port81), Since port 81 will be block in production it is impossible to go direct to site by clicking the link. Any thought about this? Thanks for help. joe
Replies
|
||||||||||||||||||||||||||||||||||||||||||||||||
Look in the file named ssf.properties (ssf/WEB-INF/classes/config)
Look for the section as follows...
##
## Web access protocol (http vs https) for generated URLs.
##
## Available values:
##
## context-http - Use info in the calling context. If no context is available assume http
## context-https - Use info in the calling context. If no context is available assume https
## http - Use http
## https - Use https
##
## Default is context-http
##
adapter.web.protocol=context-http
servlet.web.protocol=context-http
rss.web.protocol=context-http
ical.web.protocol=context-http
ssfs.web.protocol=context-http
simpleurl.web.protocol=context-http
What you want to do is to add the following to your ssf-ext.properties file:
adapter.web.protocol=context-https
servlet.web.protocol=context-https
rss.web.protocol=context-https
ical.web.protocol=context-https
ssfs.web.protocol=context-https
simpleurl.web.protocol=context-https
That should make all generated urls be forced to use https.