Results 1 to 2 of 2

Thread: Restrict access to Live HTTP Origin application

  1. Default Restrict access to Live HTTP Origin application

    We have a Wowza server configured with a Live HTTP Origin application, and a number of non-Wowza edge servers running Varnish. We want to make sure that only the edge servers can access the origin. Because of Origin Mode in the application, all outgoing connections share session, thus it's not possible to use the Client Restrictions as described in, or use onHTTPSessionCreate for that matter. We can't use IPTables to block unknown IP addresses, because we don't know the IPs of incoming RTMP streams, who use the same port.

    Any suggestions on how we can restrict access to the HTTP streams, so that only our own edge servers can pull the chunks?

  2. #2



    You can use the interface IVHostHTTPStreamerRequestValidator. This provides access to all HTTP requests inbound.


Similar Threads

  1. Restrict public access to subfolders in application content folder
    By sam.shm in forum Live Streaming and Encoders
    Replies: 2
    Last Post: 06-22-2014, 03:44 PM
  2. How to restrict access to video by url pattern
    By sam.shm in forum Live Streaming and Encoders
    Replies: 3
    Last Post: 06-22-2014, 03:31 PM
  3. WSE Manager: how to restrict access by ip ?
    By Florent.T in forum General Forum
    Replies: 5
    Last Post: 04-23-2014, 10:25 AM
  4. Restrict Access Wowza + EC2 + S3 + CloudFront
    By Tiago Tavares in forum Wowza Media Server 3 for Amazon EC2 Discussion
    Replies: 5
    Last Post: 11-25-2013, 04:34 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts