59 lines
3.3 KiB
HTML
59 lines
3.3 KiB
HTML
|
<?xml version="1.0" encoding="utf-8"?>
|
||
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
||
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
||
|
<head>
|
||
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
<meta name="dc.language" scheme="rfc1766" content="en-us" />
|
||
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
<!-- US Government Users Restricted Rights -->
|
||
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
<meta name="dc.date" scheme="iso8601" content="2005-09-06" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
<meta name="security" content="public" />
|
||
|
<meta name="Robots" content="index,follow"/>
|
||
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
<title>Application proxies</title>
|
||
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
||
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
||
|
</head>
|
||
|
<body>
|
||
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
||
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
||
|
|
||
|
<a name="appprox"></a>
|
||
|
<h3 id="appprox">Application proxies</h3>
|
||
|
<p>An application proxy or application proxy server receives requests
|
||
|
intended for another server and acts on the client's behalf (as the client's
|
||
|
proxy) to obtain the requested service. You often use an application proxy
|
||
|
server when the client and the server are incompatible for direct connection.
|
||
|
For example, the client is unable to meet the security authentication requirements
|
||
|
of the server but should be permitted some services. Characteristics of an
|
||
|
application proxy include the following:</p>
|
||
|
<ul>
|
||
|
<li>Breaks the TCP/IP connection between a client and server; IP forwarding
|
||
|
is not required.</li>
|
||
|
<li>Hides the internal client IP addresses; only the public IP address of
|
||
|
the proxy server is visible from the external network</li>
|
||
|
<li>Provides detailed access logs</li>
|
||
|
<li>Authenticates uses</li>
|
||
|
<li>Caches information</li></ul>
|
||
|
<p>The most common type of proxy is the HTTP proxy. Most HTTP
|
||
|
proxies also handle Secure HTTP (HTTPS) and file transfer protocol (FTP).
|
||
|
The SMTP mail relay is an example of an application proxy.</p>
|
||
|
<p>The main drawback of application proxies is that they must
|
||
|
support the application for which they are performing the proxy function.
|
||
|
Many TCP/IP applications are not supported by proxy servers. In addition,
|
||
|
application proxies do not typically encrypt data.</p>
|
||
|
<p> Some Universal Connection applications can flow through a
|
||
|
standard HTTP proxy. The HTTP proxy must support SSL tunneling and can optionally
|
||
|
require HTTP Basic Authentication.</p>
|
||
|
<p>i5/OS™ V5R4 includes a service and support HTTP Proxy which
|
||
|
can be used specifically for Universal Connection applications if you want
|
||
|
one partition or system providing connectivity for others.</p>
|
||
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
</body>
|
||
|
</html>
|