Redirect http to https: Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 5: | Line 5: | ||
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. | ||
On each mailbox node, in the file '''/opt/zimbra/tomcat/webapps/zimbra/public/Login.jsp''', comment out this statement: | |||
qs = emptyQs? "?initMode=" + currentProto: qs + "&initMode=" + | qs = emptyQs? "?initMode=" + currentProto: qs + "&initMode=" + | ||
| Line 14: | Line 14: | ||
//qs = emptyQs? "?initMode=" + currentProto: qs + "&initMode=" + | //qs = emptyQs? "?initMode=" + currentProto: qs + "&initMode=" + | ||
//currentProto; | //currentProto; | ||
==Set mixed mode== | ==Set mixed mode== | ||
Revision as of 15:43, 27 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.
On each mailbox node, 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;
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.
