Using Namespace Domain <Fqdn:port; Table 8 Example Namespace Domain Regex Entries - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Administrator’s guide and cli command reference
Table of Contents

Advertisement

Media Flow Controller Administrator's Guide
Table 8
Example namespace domain regex entries
www.example.com|example.com
.*example.com
^[a-f,0-9]{8}\.(origin\.|cdn\.)?cms\.example\.com:80$
^cms[0-9]{3}\.(dc2|qcg7)\.example\.com:80$
^orig.(sv1|qcg1|qcg5)\.example\.com:80$
^(cms[0-9]{3}).*(qcg[0-9]+|sv1|ch1|dc2|af1)\.example\.com:80$ cms123.x.y.qcg0.example.com:80
Using namespace domain <FQDN:Port>
Media Flow Controller can listen for requests on multiple TCP ports, up to 64; default is port 80
for HTTP, port 554 for RTSP. In order to map incoming requests to the correct namespace,
especially on a non-default port, the namespace domain MUST be set properly with port
number included. Media Flow Controller maps an incoming URL to a namespace by extracting
the value against the HOST header and matching it to the value configured for the
namespace domain.
When non-default port numbers are used you MUST ensure that the HOST header has the
port number coded correctly in the incoming URL and also in the namespace domain.
Example: If Media Flow Controller listens on port 80, 8080, and 4040 for incoming HTTP
requests; and the requests on port 80 must go to namespace ns80, those coming in on port
4040 must go to namespace ns4040, and those on port 5050 must go to namespace ns5050,
then the configuration would be as follows:
namespace ns80
domain video.example.com
namespace ns8080
domain video.example.com:4040
namespace ns4040
domain video.example.com:5050
For requests to match ns80, domain/HOST: header must be video.example.com.
For requests to match ns4040, domain/HOST: header must be video.example.com:4040.
For requests to match ns5050, domain/HOST: header must be video.example.com:5050.
Regex
Creating a Namespace and Setting Namespace Options (CLI)
Media Flow Controller Configuration Tasks (CLI)
www.example.com
example.com
abcdef02.origin.cms.example.com:80
abcdef02.cdn.cms.example.com:80
abcdef02.cms.example.com:80
cms123.dc2.example.com:80
cms123.qcg7.example.com:80
orig.sv1.example.com:80
orig.qcg1.example.com:80
orig.qcg5.example.com:80
cms123.x.y.qcg01.example.com:80
cms123.x.y.sv1.example.com:80
cms123.x.y.ch1.example.com:80
cms123.x.y.dc2.example.com:80
cms123.x.y.af1.example.com:80
Matches
83

Advertisement

Table of Contents
loading

This manual is also suitable for:

Media flow controller 2.0.4

Table of Contents