Results 1 to 4 of 4

Thread: Live Repeater Origin-Edge and HTTP Caching Origin

  1. #1

    Default Live Repeater Origin-Edge and HTTP Caching Origin


    Do you foresee any issues in setting up the origin in a live repeater origin-edge configuration as an HTTP Caching Origin? Would you recommend it?


  2. #2
    Join Date
    Dec 2007


    It should work. You may have to packetize on the edge you use for that purpose. The Application.xml /Client /StreamReadAccess should be enabled, if you create a HTTP Origin app in the Manager you will have to modify that.


  3. #3


    Any reason we cannot continue to packetize on the origin? It seems to work fine. The reason we are considering setting the origin as an HTTP caching origin is because our wowza edges are load balanced and if a user viewing an HLS stream gets routed to a different edge midway, that new edge should be able to continue serving the chunks.

  4. #4
    Join Date
    May 2013


    What load balancer are you using? Depending on which, you may be able to set a timeout that it uses on a per connection basis to ensure there is no switching servers after a connection is initiated until that threshold is met.

Similar Threads

  1. HLS Live Streaming origin-edge repeater
    By PaltopVince in forum Live Streaming and Encoders
    Replies: 4
    Last Post: 09-02-2016, 09:43 AM
  2. Parameter of HTTP caching origin
    By hungnguyen88 in forum Live Streaming and Encoder Discussion
    Replies: 3
    Last Post: 11-12-2013, 08:15 PM
  3. Disconnecting the current session between a live repeater edge and the origin
    By vjagannathan in forum Live Streaming and Encoder Discussion
    Replies: 6
    Last Post: 11-12-2013, 02:39 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