title: WCF netHttpBinding on Windows 7
body: <p>I currently have a client/server application written in .NET 4.0 using WCF with a netTcpBinding to provide full duplex messaging between my servers and my client applications. The server is a self hosted application up on AWS EC2. The client is a Window 7 application installed on my customers PCs.</p>
  
  <p>The problem I now have is that one of my new customers is insisting that my applications connects via their in house MS ISA 2004 Proxy server rather than going straight out to the Internet to connect to my servers.</p>
  
  <p>Problem 1:</p>
  
  <p>netTcpBinding is not Proxy aware. I have suggested that the customer installs MS Firewall Client for ISA Server to route all winsock traffic via the proxy and to simply add a new allowed protocol to the proxy server. Apparently this is not possible as the machines in the building are too locked down to install this software so this is not an option. (Hmmmmm)</p>
  
  <p>Problem 2:</p>
  
  <p>I had the bright idea of upgrading to .NET 4.5 and changing to netHttpBinding allowing for Duplex communications over HTTP using WebSockets so a proxy should just allow this through. My server is Windows Server 2012 so not problem. All works well on Windows 8. The problem I have is that non of my customers use Windows 8 and are unlikely to for a number of years. Currently netHttpBinding is only supported on Windows 8 and Server 2012. (Annoying!)</p>
  
  <p>The question I have is does anyone know of a third party library I can use to produce a custom WCF binding in .NET 4 that will allow me to connect to a .NET 4.5 netHttpBinding or can anyone point me in the direction of any other way to overcome this proxy issue whilst retaining duplex communications?</p>