April 12, 2014

Wowza statistics behind reverse proxy

There are use cases when a media streamer is putting Wowza Streaming Engine behind the reverse proxy. This is usually done for security reasons. This usually works good.

But there is a side effect of this solution. For each connection, Wowza gets the IP of the proxy instead of IP of the viewer. This means that geo-location reporting for Wowza would be shown incorrectly. Also, WMSPanel hotlinking protection for Wowza streams will not work since its hash is based on IP as well.

For HTTP-based protocols like HLS, MPEG-DASH, HDS and SMOOTH this can be solved via processing X-Forwarded-For header which Wowza provides.

We've recently added processing capability option to WMSPanel agent handle this HTTP header. You need to follow these easy steps.

1. Open Server.xml file and add the following property.
<Properties>
    <Property>
        <Name>PanelCdnOrigin</Name>
        <Value>true</Value>
    </Property>
</Properties>
2. Restart Wowza.

That's it. WMSPanel agent will be obtaining customers' IP addresses correctly.

Please notice that HTTP header is available in Wowza versions 3.x and later. Contact us if you face any difficulties with the setup.

Read more about WMSPanel streaming reporting.

Related documentation


WMSPanel, Control panel for Wowza Streaming Engine 4End user reporting for WowzaWMSPanel examples and case studyPaywall for WowzaDispersa streams monitoring

No comments:

Post a Comment