So far, I used the following method.
acl is_for_remail path_reg ^/Microsoft-Server-ActiveSync
use_backend bk_remail_cert if is_for_remail
On Sun, Aug 16, 2015 at 10:58 PM Roman Gelfand rgelfa...@gmail.com wrote:
Thanks for your help. So, it appears that in certain instances a POST is
Thanks for your help. So, it appears that in certain instances a POST is
done using relative path or URN. The question is how do I tell haproxy
that this is related to the original url that is found on the certificate.
Meaning, this part I need to change so that the forwarding is done based on
On Wed, Aug 12, 2015 at 6:34 PM, Roman Gelfand rgelfa...@gmail.com wrote:
Why would the following apache directives cause problems for haproxy.
RewriteRule ^/Microsoft-Server-ActiveSync /rpc.php
[PT,L,QSA]
RewriteRule .* -
Describing the issues you think it's causing fire haproxy would also be
helpful.
On Aug 12, 2015 4:37 PM, Baptiste bed...@gmail.com wrote:
On Wed, Aug 12, 2015 at 6:34 PM, Roman Gelfand rgelfa...@gmail.com
wrote:
Why would the following apache directives cause problems for haproxy.
I am not seeing a response to the following post. The apache backend server
show now trace of the post request, below.
Aug 12 22:43:43 localhost haproxy[15606]: 38.105.236.253:59539
[12/Aug/2015:22:43:12.935] farm_test_ssl~ bk_remail_cert/remail
26582/0/1/3530/30113 200 1229 - - 1/1/0/0/0
The NOSRV in the logs you posted, means that haproxy doesn't believe
there is a server available on the backend to fulfull the request.
The first request hits the bk_remail_cert backend, but the next two
requests don't, my guess is that the requests don't match your
use_backend requirements,
Why would the following apache directives cause problems for haproxy.
RewriteRule ^/Microsoft-Server-ActiveSync /rpc.php
[PT,L,QSA]
RewriteRule .* -
[E=HTTP_MS_ASPROTOCOLVERSION:%{HTTP:Ms-Asprotocolversion}]
RewriteRule .* -
7 matches
Mail list logo
