Hi!
On 11/30/2016 02:44 PM, Zhang Huangbin ([email protected]) wrote:
Try this: in Apache config file for ‘http://', add a rewrite rule to redirect to https like below: RewriteRule /SOGo(.*) https://%{HTTP_HOST}%{REQUEST_URI}
I've done that, and it helps, everything is https now. However, I've also started to get many lines like:
ov 30 21:11:39 sogod [957]: <0x0x7f44bc1e8570[SOGoCache]> an error occurred when caching value for key 'session:1AUsEf1JXP8CMEAUYYYlfg==': "SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY" Nov 30 21:11:39 sogod [957]: <0x0x7f44bc1e8570[SOGoCache]> an error occurred when caching value for key 'username+dn': "SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY" Nov 30 21:11:39 sogod [957]: <0x0x7f44bc1e8570[SOGoCache]> an error occurred when caching value for key 'username+attributes': "SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY" Nov 30 21:11:39 sogod [957]: <0x0x7f44bc1e8570[SOGoCache]> an error occurred when caching value for key 'SOGo+attributes': "SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY
And the SOGo gui becomes slow and unusable. (but https) :-) Removing the line, everything back to normal. Any idea why the bad side-effect? And also: why the normal way to get SOGo on https seems to be ignored? MJ -- [email protected] https://inverse.ca/sogo/lists
