+netconf-dev (because this is really more of a restconf than a dlux topic) Controller & netconf-dev for restconf teams,
To me it seems curious that we would expect an end-user to go through the "hoops" explained on the Wiki page mentioned below to get CORS working... I'm not an expert on this topic, but have dealt with CORS issues when accessing other REST APIs in past lives. From what I understand, I'm not sure if there is a real downside to just enable this CORS configuration for the web container in ODL by default - thoughts, -1 / +1? Tx, M. -- Michael Vorburger <vorbur...@redhat.com> | IRC: vorburger @freenode | ~ = http://vorburger.ch On Fri, Oct 28, 2016 at 3:37 PM, 徐鸿 <iceh...@gmail.com> wrote: > Hi, dear all, > > I am using opendaylight beryllium version to do a demo test, and I am > totally know nothing about AngularJS, so I want do ajax call form another > static web page. Then I got the CORS error. > > I want to open CORS support to my controller , and follow such guide : > https://wiki.opendaylight.org/view/OpenDaylight_Controller:CORS_support > > My question is : > 1. Is the new feature 'myfeature' is a MUST to open CORS ? > 2. In the begining of the wiki, it said 'Compile odlparent, yangtools and > controller', but why I can't find the steps about how to change? > 3. Is it possible to open CORS in the distribution package without > compile controller project ? > 4. If compile controller can't be avoid, what is the minimized steps to > copy the target jars to distribution package ? > > Any reply will be very much appreciated， Thanks . > > yours, Hong Xu > > _______________________________________________ > controller-dev mailing list > controller-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/controller-dev >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
