SSL Proxy
proxy server Also called a "proxy," it is a computer system or router that breaks the connection between sender and receiver. Functioning as a relay between client and server, proxy servers help prevent an attacker from invading a private network and are one of several tools used to build a firewall.
The word proxy means "to act on behalf of another," and a proxy server acts on behalf of the user. All requests from clients to the Internet go to the proxy server first. The proxy evaluates the request, and if allowed, re-establishes it on the outbound side to the Internet. Likewise, responses from the Internet go to the proxy server to be evaluated. The proxy then relays the message to the client. Both client and server think they are communicating with one another, but, in fact, are dealing only with the proxy.
An SSL termination proxy is a proxy server that is used by an institution to handle incoming SSL connections, decrypting the SSL and passing on the unencrypted request to the institution's other servers. SSL termination proxies are used to reduce the load on the main servers by offloading the cryptographic processing to another machine. Wikipedia uses Nginx as its SSL termination proxy.
Address Translation and Caching ď Ź
The SSL private proxy server is a dual-homed host with two network interfaces and two IP addresses. The IP address on the outbound side of the proxy is the one the Internet sees, and the address of the machine making the request is hidden to the outside world. Proxies are often used in conjunction with network address translation (NAT), which hides all the IP addresses of the client machines on the internal network. Proxy servers may also cache Web pages, so that the next request for that same page can be obtained much faster locally.
Advantages of Supporting HTTPS with SSL in Addition to HTTP
If you configure your deployment of TFS to support both protocols, users whose computers have been configured for HTTPS with SSL will connect by using that protocol, which makes your deployment more secure to buy proxy. In addition, users whose computers are configured for HTTP only can still connect to your deployment. Although you should not deploy this configuration over public networks, you can gain the following advantages by continuing to support HTTP connections in a controlled network environment:
You can increase the security of your deployment over time by configuring client computers for HTTPS with SSL as your schedule permits. If you take a phased approach, you do not need to upgrade all computers at the same time, and users whose computers have not yet been upgraded can still connect to the deployment. You can more easily configure and maintain Team Foundation Server. Calls from one Web proxy server to another are faster over HTTP than over HTTPS with SSL. Therefore, you can continue to support HTTP connections from client computers for which the performance requirements outweigh the security risks.
Advantages of Requiring HTTPS with SSL for All Connections
All web connections between the application tier, the data tier, and the client tier for Team Foundation are more secure because they require certificates. You can control access more easily by configuring certificates to expire when a project phase is expected to end with anonymous proxy.
Disadvantages of Supporting or Requiring HTTPS with SSL
You might complicate ongoing administration tasks. For example, you might have to reconfigure your deployment to stop supporting HTTPS with SSL before you can apply service packs or other updates. You must not only configure but also manage a certification authority (CA) and certificate trusts with Private proxy. You can use Certificate Services in Windows Server 2003 and Windows Server 2008, but you might not want to invest the time and resources that deploying a secure public key infrastructure (PKI) requires.
You must spend significant time setting up and testing either of these configurations, and troubleshooting your deployment will become more difficult. If you continue to support both protocols, external connections might not be encrypted if the application tier for Team Foundation is not appropriately secured. If you require HTTPS with SSL with private proxy server, your deployment's performance will be slower.
Thanking you!!! For more info log on too... http://proxiesforent.com