# Cross-Origin Edit Error

**URL:** <https://community.wowza.com/t/cross-origin-edit-error/45596>\
**Category:** Wowza Streaming Engine\
**Tags:** server-administration\
**Created:** [May 3, 2016, 9:52am UTC](https://community.wowza.com/t/cross-origin-edit-error/45596 "2016-05-03T09:52:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cory\_Savit](https://avatars.discourse-cdn.com/v4/letter/c/c37758/32.png) [@Cory\_Savit](https://community.wowza.com/u/Cory_Savit)\
**Post date:** [May 3, 2016, 9:52am UTC](https://community.wowza.com/t/cross-origin-edit-error/45596/1 "2016-05-03T09:52:54Z")

</div>

Hi everyone,

I am trying to changing CORS settings to allow get requests for an HLS stream. Running some tests with the [HLSJS](https://flowplayer.org/docs/plugins.html#hlsjs) plugin for Flowplayer.

Anyway, when I go to WowzaStreamingEngine Manager -\> Applications -\> Live -\> Setup -\>

Then check “Cross-origin resource sharing (CORS) (for HTTP-based streams)” under Options, and click the Save button, the next page returns this error:

```auto
Invalid property 'streamConfig' of bean class [com.wowza.wms.webapp.application.ApplicationModel]: Bean property 'streamConfig' is not readable or has an invalid getter method: Does the return type of the getter match the parameter type of the setter?

```

Even though there is a Stack Trace header on this page, no stack trace is displayed (would be helpful…).

We recently upgraded from 4.1.0 to 4.4.1 , but have not seen any other problems. I haven’t changed these settings since the original setup years ago, so I can’t say whether this error is due to the upgrade or not.

Any help would be appreciated.

---

<div class="post-metadata">

**Author:** ![Jason\_Hatchett](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/jason_hatchett/32/391_2.png) [@Jason\_Hatchett](https://community.wowza.com/u/Jason_Hatchett)\
**Post date:** [May 10, 2016, 2:37am UTC](https://community.wowza.com/t/cross-origin-edit-error/45596/2 "2016-05-10T02:37:51Z")

</div>

Hello,

I am unable to reproduce this error so this could be an issue with a setting that was carried over from an older installation.

Can you try recreating the application inside Wowza Streaming Engine Manager using the base Live application option and see if you still get this error?

Regards,

Jason Hatchett