247
FLASH
MEDIA
SERVER
4.5
CONFIGURATION
AND
ADMINISTRATION
XML configuration files reference
Last updated 11/28/2012
The connection syntax for this element is flexible, as demonstrated in the following examples.
Examples
This example shows how you can configure the edge to route all connections to the host
foo
to the host
bar
.
<Proxy>
<RouteTable protocol="">
<RouteEntry>foo:1935;bar:80</RouteEntry>
</RouteTable>
</Proxy>
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>*:*;foo:1935</RouteEntry>
The example instructs the 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>*:*;*:1936</RouteEntry>
The example instructs the 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>*:*;*:80</RouteEntry>
The example instructs the server to route a host:port combination to
null
. Its effect is to reject all connections destined
for
foo:80
.
<RouteEntry>foo:80;null</RouteEntry>
See also
RouteTable
RouteTable
Container element.
<RouteTable protocol="rtmp">
or
<RouteTable protocol="rtmps">
The
RouteEntry
elements nested under the
RouteTable
element specify the routing information for the edge server.
Administrators use these elements to route connections to the desired destination. The
RouteTable
element can be
left empty or it can contain one or more
RouteEntry
elements.
The
protocol
attribute specifies the protocol to use for the outgoing connection. The attribute is set to
""
(an empty
string),
rtmp
for a connection that isn’t secure, or
rtmps
for a secure connection.
•
Specifying
""
(an empty string) means preserving the security status of the incoming connection.
•
If the incoming connection was secure, then the outgoing connection will also be secure.
•
If the incoming connection was not secure, the outgoing connection will not be secure.
•
Specifying
rtmp
instructs the edge not to use a secure outgoing connection, even if the incoming connection was
secure.