![]() Use_backend be_ex2016_autodiscover if autodiscover Redirect scheme https code 301 if ! # redirect 80 -> 443 (for owa)Īcl eas url_beg /Microsoft-Server-ActiveSync Http-response set-header X-Content-Type-Options nosniffīind aaa:bbb:cccc:dddd::30:80 transparentīind 1.2.3.4:443 ssl crt /etc/ssl/certs/exchange.pemīind aaa:bbbb:cccc:dddd::30:443 transparent ssl crt /etc/ssl/certs/exchange.pem Http-response set-header X-Frame-Options SAMEORIGIN ![]() Timeout server 15m # this value should be rather high with Exchange Timeout client 15m # this value should be rather high with Exchange Option redispatch option contstats retries 3 Ssl-default-server-ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:RSA+AESGCM:RSA+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS ![]() Ssl-default-bind-ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:RSA+AESGCM:RSA+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS Haproxy version 2.0.8 on Debian Buster, Exchange 2016 (migrated from 2010), all the namespaces point to, had a round robin DNS (yeah I know it’s 2019) which worked, won’t say perfectly but decently on the non caching ISPs, the caching ones… The only error I get is Can’t connect to Exchange, mailbox unavailable (pardon, don’t recall the excact error), outlook logging stops after autodiscover and nothing in the logs, seems like it won’t connect to the DAG. The one issue I have is OA - RPC over HTTPS is not working on L7 configuration. Hello, I’m very new to haproxy, managed to get a working configuration by combining a week of Googling and surfing the web. ![]()
0 Comments
Leave a Reply. |