Results 1 to 6 of 6

Thread: HTTP Live Origin and Varnish

  1. #1

    Default HTTP Live Origin and Varnish

    I setup Wowza 4.0.4 HTTP Live Origin application and use Varnish to cache and test.

    It seems Varnish does not really cache anything.

    I use 10 browsers and request to varnish the same stream.

    In theory, Varnish will get content from Wowza, cache and serve to 10 clients at the same time. If this was the case, the input and output bandwidth would be 10 fold different. My stream is 1Mbps so the input (get content from Wowza) should be 1Mbps and output to 10 clients should be 10Mbps.

    However when I tested, the input and output always the same. If I use 10 clients to request, then input will be 10Mbps and output will be 10Mbps. It means varnish does not really cache, or the caching is too short.

    I setup HTTP Live Origin as instructed in the Article and here is the HLS configuration

    <!-- Properties defined here will override any properties defined in conf/LiveStreamPacketizers.xml for any LiveStreamPacketizers loaded by this applications -->
    <!-- Properties defined here will override any properties defined in conf/HTTPStreamers.xml for any HTTPStreamer loaded by this applications -->

    Does anyone has experience in this HTTP Live Origin setup?


  2. #2


    Hello there,

    Please open a support ticket on this matter by zipping up the following directories and sending them to Please also include a link to this thread as reference:

    Thank you,


  3. #3


    have you got it working?

  4. #4
    Join Date
    Aug 2014


    Hi Robertookala,

    Varnish can cache anythings from Wowza, include Video On Demand and Live Streaming. I checked. But you must use the HTTP Origin Streaming(This features need a license). If you use other features in wowza, it can not run exactly.

    If you don't have a license in wowza, you can send a request to wowza and get a trial full (remember trial full). It will run exactly what you thinking.


    TRAN Anh Dung
    Last edited by trandung410; 12-18-2015 at 12:53 AM.

  5. #5
    Join Date
    Jan 2016


    "Caching" won't work if httpRandomizeMediaName is set to true because each chunk will have a unique name ...

  6. #6
    Join Date
    Jan 2015



    To add more details, httpRandomizeMediaName is used for live streams in origin mode so that old chunks are not returned when a stream restarts on the server. When a packetizer starts or restarts, its chunk index will start at 1. Without random names, the playlist will return the default name and the cache may already have an old file cached with the same name. With httpRandomizeMediaName set, each time the packetizer is started or restarted, a different name will be used for the actual chunks.

    There are several reasons as to why your HTTP Origin streaming workflow may not be working with Varnish, including an incorrect license key (standard trial keys do not have this feature), incorrect settings on the cache server, misconfigured Wowza server, etc. As Sal has mentioned, sending your Wowza conf and logs would allow us to investigate further.


Similar Threads

  1. Live HTTP origin
    By rayharris in forum Suggestions
    Replies: 8
    Last Post: 03-03-2016, 01:05 PM
  2. Replies: 1
    Last Post: 06-30-2014, 04:20 AM
  3. Live Repeater Origin-Edge and HTTP Caching Origin
    By vjagannathan in forum General Forum
    Replies: 3
    Last Post: 06-18-2014, 02:56 AM
  4. Live HLS fragments getting cached by the browser (HTTP Origin mode)
    By Florent.T in forum Live Streaming and Encoders
    Replies: 5
    Last Post: 06-08-2014, 07:51 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