Nginx as proxy for Exchange 2013 : RPC?

I’ve been searching the internet and tried a few approaches, but I was
wondering:

Is it possible to use Nginx (non-plus edition) as a proxy for Exchange
(2013) - in particular: RPC. I did manage to get the other stuff
working.
Maybe by installing/enabling a (free) module?

If so, would someone be so kind to share a working config?

Posted at Nginx Forum:

Posted at Nginx Forum:

It doesn’t seem to mention the RPC (not RDP)?

Posted at Nginx Forum:

So I just need a stream and proxy_pass it to our Exchange? (I’m new to
Nginx, haven’t seen stream config before; we’re using SSL for
everything).

Also, is it possible to have a combination? The deal is: the current
setup
in our company is only 1 public IP address for a couple of services.
Which
used to be fine, since SSL was only used for Exchange (and our firewall
was
configured to only send the HTTP-traffic to the Nginx, and HTTPS to
Exchange). But now, I need to able to split it out, based on the names (
apps.domain.ext and mail.domain.ext ).

Posted at Nginx Forum:

If data is a tcp stream use stream, if not then a http {} block should
work.

Posted at Nginx Forum:

I’ve had most success so far with this approach (Tigunov’s config -
https://gist.github.com/taddev/7275873).
( btw, I’m using Basic Authentication rather than NTLM ).

server {
server_name mail.contoso.com;
server_name autodiscover.contoso.com;
keepalive_timeout 3h;
proxy_read_timeout 3h;
#reset_timedout_connection on;
tcp_nodelay on;
listen 443 ssl;
client_max_body_size 3G;
#proxy_pass_header Authorization;
proxy_pass_header Date;
proxy_pass_header Server;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Accept-Encoding “”;
proxy_pass_request_headers on;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_http_version 1.1;
proxy_request_buffering off;
proxy_buffering off;
proxy_set_header Connection “Keep-Alive”;

location / {
        proxy_pass https://exchange.internal/;
        proxy_next_upstream error timeout invalid_header http_500

http_503;
}

}

With Microsoft’s Remote Connectivity Analyzer, I now get up to the
point
where ActiveSync is tested. “OPTIONS” works, FolderSync fails (
something
about a request being aborted or canceled, no further details ).

Posted at Nginx Forum: