IIS Reverse proxy and websockets, failed websocket handshake

Is 'localhost' on the same server? i.e. is Tomcat on port 9443 while ARR is on port 80, on the same server?

Here are the key things to setup:

• create a Server Farm. If it's on the same box, add a single node pointing to 'localhost'.
• if you say 'yes' to create the URL Rewrite rules, it will capture all traffic and forward to that server farm. If that's fine, then say yes.
• if you didn't create the URL Rewrite rule in the previous step, then go to the top level of IIS, go to URL Rewrite, and create a new rule. Use {HTTP_HOST} for the domain name, or {SERVER_ADDR} for the IP binding. Set the action to use the Server Farm you set up in the first step above.
• the Default Web Site should catch all traffic, which in turn will be caught by the URL Rewrite rule at the global level.

Yes, this web.config "script" from Cloudflare does affect logging by capturing the IP address of the client (connecting) user that connected to the proxy and delivers it to your destination server via the server variable REMOTE_ADDR. Otherwise, you'd see the IP address of the proxy server as the requesting IP address.

I think this will work with ASP.NET applications but will NOT work with PHP applications. For those I would think you would need something along the lines of:

http://drupal.org/project/cloudflare (though I realize that is Drupal specific it is basically a PHP version of the ASP.NET way you listed)

The reason the F5 solution exists is to handle this on the Proxy Server side. Both the ASP.NET solution listed here, and the PHP solution listed for Drupal seem to be utilizing a value that CloudFlare is forwarding (HTTP_CF_Connecting_IP) and are intended to be used on the destination server.

I realize it has been a while since you asked this question but I figured this answer might help others even if you've already arrived at an answer/solution.