Streaming Media Supplement sa2150 and sa2250

97
Chapter 9 Configuring Media-IXT for QuickTime
Assuming that this is so, and that the origin RealNetworks server answers to back.myreality.com,
our rules would be:
map rtsp://front.myreality.com/ rtsp://back.myquickness.com/ QT
map rtsp://front.myreality.com/ rtsp://back.myreality.com/ RNI
4. After we modify the remap.config file, Traffic Manager must reread the configuration files. From
Media-IXT’s
bin directory, run the command:
traffic_line -x
A port number appears in a remapping rule for reverse proxy only when the port used for the rule’s protocol is
a non-standard port. So, if you use port 1091 for RTSP, which is Media-IXT’s standard port for that protocol,
your map rule takes this form:
map rtsp://front.myreality.com/ rtsp://back.myquickness.com/
If you use a non-standard port for RTSP, say 9090, the rule must specify the port:
map rtsp://front.myreality.com:9090/ rtsp://back.myquickness.com/
Configuring reverse proxy for QuickTime and RealNetworks simultaneously
A single Media-IXT can perform reverse proxy for both RealNetworks and QuickTime origin servers
simultaneously. By adding a designator to a reverse proxy mapping rule in the remap.config file, you can
determine that the rule applies exclusively to either RealNetworks or QuickTime content.
You can do this either through Traffic Manager or by manually editing remap.config.
The extra field appears at the end of an entry in remap.config and may have the value RNI for
RealNetworks, or QT for QuickTime.
These example remap.config entries would enable remapping of requests:
• from RealPlayer clients to an origin RealServer called actual-rni-server.com
• from QuickTime Player clients to an origin QuickTime server called actual-qt-server.com
map rtsp://rniserver.com rtsp://actual-rni-server.com RNI
map rtsp://qtserver.com rtsp://actual-qt-server.com QT
Configuring selective caching for QuickTime
Using selective caching, you specify criteria to determine whether to proxy certain content or not, and whether
to cache certain content or not.
When content is not proxyable, Media-IXT denies the client connection, with an appropriate message to the
client (if possible).
When content is not cacheable, Media-IXT goes into passthrough mode and proxies, but does not cache, the
content.
See the HP Cache Server Appliance Administrator Guide for more information about selective caching.
NOTE For RealNetworks and QuickTime, remapping rules use Media-IXT’s hostname and not
its IP address. Only WMT remapping rules use Media-IXT’s IP address.
NOTE In a standard configuration, you should never need to specify a port number in either the
URLs or the remap rules for RealNetworks streams.