A reverse edge server hides the presence and location of the origin server. Administrators can explicitly determine that connection requests to Flash Media Server be automatically routed through a reverse edge or proxy server. You can use RTMPS to configure a reverse proxy to listen on port 80 for non-secure connection requests and port 443 for secure requests.
For example, if your applications are running on fms-secure.foo.com, you can direct the connection requests from clients’ devices or computers to the proxy server (or virtual host) called fms.foo.com, which makes the connection to fms-secure.foo.com, where your applications are running. The client is not aware that its request is being sent to another server.
The Flash Media Server or network administrator specifies the routing information for a proxy or edge server in the RouteEntry tags of the Vhost.xml configuration file.
Administrators use the Vhost.xml file to configure how and where to route connections to the desired destination.
The protocol attribute in the RouteEntry tag specifies the protocol of the outgoing connection. This attribute must be set to either "rtmp" or "rtmps" to indicate a nonsecure or secure connection.
The RouteTable container tag holds all the RouteEntry tags. For example, the RouteTable container may hold one RouteEntry tag to specify a secure outgoing connection by using RTMP, and another RouteEntry tag that specifies the nonsecure RTMP connection. If a protocol is not specified, the outgoing connection uses the same protocol as the incoming connection.
For detailed information on these routing tags, see “Vhost.xml file” in Managing Flash Media Server.
Clients can explicitly connect to a specific edge server when they know it is available. You use a URI in a wrapped format to make the connection to an explicit proxy: rtmp://edge/?rtmp://origin/app
You can also connect to a chain of proxies by forming a string that routes the outgoing connection requests through a sequence of explicitly identified proxies:
rtmp://edge1/?rtmp://edge2/?rtmp?://edge3/?rtmp://edge4/?rtmp://origin/app
As the connection moves through each edge in the chain, Flash Media Server drops the first token in the string. After making the connection to edge1, the connection string changes to:
rtmp://edge2/?rtmp?://edge3/?rtmp://edge4/?rtmp://origin/app
Flash Player 8 automatically detects any edge servers in its proximity. When an edge server is available, Flash Player automatically routes the connection from the client to the origin server through the proxy server. These edge servers are defined as implicit proxies since the client is generally unaware that its communication with Flash Media Server is being routed through a proxy. This use of an implicit proxy allows your current applications to continue working without any changes. Flash Player exposes the proxy information to the client only through the read-only properties on the NetConnection object.
For more information on the NetConnection class, see the Client-Side Media ActionScript Language Reference.
|
|
|
You can chain together any number of edges when you make connections to the origin server. The following URI shows how two explicit proxies are chained together to direct connection requests to the origin server:
rtmp://proxy1/?rtmp://proxy2/?rtmp://origin/app/inst
When you use URL decoration to chain proxies, Flash Player 7 and earlier versions may have problems with shared objects because of the embedded question mark (?) character in the URL.
A workaround is available for clients who use earlier versions of Flash Player. You can resolve the problem by using the following function to escape the question marks from the URI before passing the URI to the shared object.
Уважаемый посетитель!
Чтобы распечатать файл, скачайте его (в формате Word).
Ссылка на скачивание - внизу страницы.
