Re: [osgi-dev] Enroute Rest

2016-11-10 Thread Peter Kriens
t: 10 November 2016 10:48 > To: OSGi Developer Mail List <osgi-dev@mail.osgi.org > <mailto:osgi-dev@mail.osgi.org>> > Subject: RE: [osgi-dev] Enroute Rest > > ยท Do we have option to set HTTP Header set > Access-Control-Allow-Origin "*" on the Jett

Re: [osgi-dev] Enroute Rest

2016-11-10 Thread manoj.vrajamani
rid of this CORS (Cross Origin Resource Sharing) issue ? Please advise.. Thanks.. -Manoj From: Manoj Venkatesh Rajamani (Product Engineering Service) Sent: 10 November 2016 10:48 To: OSGi Developer Mail List <osgi-dev@mail.osgi.org> Subject: RE: [osgi-dev] Enroute Rest * Do we have

Re: [osgi-dev] Enroute Rest

2016-11-09 Thread manoj.vrajamani
> Subject: Re: [osgi-dev] Enroute Rest ** This mail has been sent from an external source ** You can read about CORS here: https://en.wikipedia.org/wiki/Cross-origin_resource_sharing Regards, Neil On 9 Nov 2016, at 11:51, <manoj.vrajam...@wipro.com<mailto:manoj.vrajam...@wipr

Re: [osgi-dev] Enroute Rest

2016-11-09 Thread Neil Bartlett
You can read about CORS here: https://en.wikipedia.org/wiki/Cross-origin_resource_sharing Regards, Neil > On 9 Nov 2016, at 11:51, > wrote: > > Hi All, > > I am trying to

[osgi-dev] Enroute Rest

2016-11-09 Thread manoj.vrajamani
Hi All, I am trying to retrieve an http response (json string) from an osgi app implementing enroute rest api. When i write a client html app and invoke the osgi app, it gets invoked and returns the string. But I get a warning as below and I am unable to see the text in my browser page.