Results 1 to 2 of 2

Thread: Enable cross-origin resource sharing (CORS) in a startup package?

  1. #1
    Join Date
    Aug 2015

    Default Enable cross-origin resource sharing (CORS) in a startup package?

    Our church runs Wowza 4.4.1 on EC2 using the legacy DevPay AMIs. We're already using a startup package to set passwords and whatnot, and it works well. Now we'd like to enable CORS (Applications -> Live -> Cross-origin Resource Sharing) automatically at startup, rather than having to manually enable it through the Engine Manager each week.

    Does anyone have an example for me?


  2. #2



    By following this article:

    Once you set up your application with CORS enabled, you should not have set this up again, unless you are taking down your instance each week and then recreating it every time you need to use it.

    After setting this through the Streaming Engine Manager a property is added to the Application.xml under HTTPStreamer properties.


    If you are recreating your instance each week you can try to script this entry into your Application.xml.

    Jason Hatchett

Similar Threads

  1. Enable CORS for main page
    By shaunbowe in forum General Forum
    Replies: 1
    Last Post: 12-23-2015, 10:10 AM
  2. Enable CORS Access-Control-Allow-Origin for DASH
    By f.hernandez.b in forum Live Streaming and Encoders
    Replies: 3
    Last Post: 09-16-2015, 06:22 PM
  3. How do i set up Cross-Origin Resource Sharing in Wowza?
    By j-developer in forum On-Demand Streaming
    Replies: 1
    Last Post: 05-03-2014, 12:48 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