
178 Configuration Files
Description
Proxies or edge servers are configured with the RouteEntry tag to direct connections to
another destination. The
RouteTable tag contains the RouteEntry tags that control where
the edge or proxy server reroutes requests.
You can also add the
protocol attribute to an individual RouteEntry tag to specify how the
the edge or proxy server reroutes requests. If no protocol is specified, however, Flash Media
Server applies the protocol specified in the
RouteTable tag. Implicit proxies hide the routing
information from the clients.
The connection syntax for this tag is flexible, as demonstrated in the following examples.
Examples
<Proxy>
<RouteTable protocol=””>
<RouteEntry>foo:1935;bar:80</RouteEntry>
</RouteTable>
</Proxy>
This example shows how you can configure the proxy to route all connections to the host
“foo” to the host “bar.”
<RouteEntry>*:*;foo:1935</RouteEntry>
Flash Media Server allows the use of the wildcard character '*' to replace host and port.The
example shows how to route connections destined for any host on any port to port 1935 on
the host
“foo.”
<RouteEntry>*:*;*:1936</RouteEntry>
The example instructs Flash Media Server to route connections to any host on any port, to the
specified host on port 1936. For example, if you were to connect to
"foo:1935", the
connection would be routed to
"foo:1936".
<RouteEntry>*:*;*:80</RouteEntry>
The example instructs Flash Media Server to use the values for host and port on the left side as
the values for host and port on the right side, and to route connections destined for any host
on any port to the same host on port 80.
<RouteEntry>foo:80;null</RouteEntry>
The example instructs Flash Media Server to route a host:port combination to null. Its effect
is to reject all connections destined for
foo:80.
See also
Proxy container, Anonymous, Mode, RouteTable tags
Commentaires sur ces manuels