[ 
https://issues.apache.org/jira/browse/UNOMI-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391121#comment-16391121
 ] 

Serge Huber commented on UNOMI-170:
-----------------------------------

Hello Mitesh,

The buildAndRun.sh doesn't work right now because I'm still working on some 
issues in the integration tests. Please use the buildAndRunNoTests.sh for the 
time being. Also you need to make sure you have a properly setup [ElasticSearch 
5.6.3|https://www.elastic.co/fr/downloads/past-releases/elasticsearch-5-6-3] 
with a cluster.name: contextElasticSearch in the config/elasticssearch.yml

Could you post the details of the error that you got ? 

Best regards,

  Serge... 

> UNOMI CORS Issue is coming when trying to fetch RULES
> -----------------------------------------------------
>
>                 Key: UNOMI-170
>                 URL: https://issues.apache.org/jira/browse/UNOMI-170
>             Project: Apache Unomi
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.2.0-incubating, 1.3.0-incubating
>         Environment: Mac OS
>            Reporter: Mitesh Jain
>            Priority: Major
>              Labels: security
>         Attachments: Screen Shot 2018-03-07 at 11.35.27 AM.png
>
>
> Hi,
> My Name is Mitesh Jain,
> I am new to Unomi.
> All installations are done according to this link:
> [http://unomi.incubator.apache.org/]
> When I am trying to access the rest api cxs to fetch all the rules, it is 
> showing properly in browser when I browse,
> [https://localhost:9443/cxs/rules]
> but when I am trying to access the same using my Angular application to fetch 
> rules using above url, 
> [https://localhost:9443/cxs/rules|https://localhost:9443/cxs/rules/] it will 
> make a OPTIONS call and I am getting the error as "No 
> 'Access-Control-Allow-Origin' header is present on the requested resource."
> Please Let me know how to fix this CORS issue.
> Mitesh Jain
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to