Redirect http to https: Difference between revisions
mNo edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
This will allow initial connections over http, but '''always''' redirect them to https. If you just want to force authentication to occur over https, just use ''[[zmtlsctl]] mixed''. | This will allow initial connections over http, but '''always''' redirect them to https. If you just want to force authentication to occur over https, just use ''[[zmtlsctl]] mixed''. | ||
==Edit Login. | ==Edit Login.jsp== | ||
This prevents the server from redirecting back to http if the initial connection is http. | This prevents the server from redirecting back to http if the initial connection is http. |
Revision as of 15:46, 13 March 2007
This will allow initial connections over http, but always redirect them to https. If you just want to force authentication to occur over https, just use zmtlsctl mixed.
Edit Login.jsp
This prevents the server from redirecting back to http if the initial connection is http.
In the file /opt/zimbra/tomcat/webapps/zimbra/public/Login.jsp, comment out this statement:
qs = emptyQs? "?initMode=" + currentProto: qs + "&initMode=" + currentProto;
In other words, make it look like this:
//qs = emptyQs? "?initMode=" + currentProto: qs + "&initMode=" + //currentProto;
Network Edition Users: Be aware that each node of the cluster needs to have this change applied.
Set mixed mode
This configures the server to accept both http and https connections.
su - zimbra zmtlsctl mixed tomcat restart
Note that this is an attempt at a workaround for the problem addressed in Bug 7631, which is scheduled to be fixed in ZCS 5.0.