Melanie Reiplinger created STANBOL-712:
------------------------------------------

             Summary: CORS access to the Rules endpoint
                 Key: STANBOL-712
                 URL: https://issues.apache.org/jira/browse/STANBOL-712
             Project: Stanbol
          Issue Type: Wish
          Components: Rules
            Reporter: Melanie Reiplinger


It would be great if full CRUD access via CORS could be granted in the near 
future. Overview of what I tested so far: 

CORS access (PUT, DELETE, POST, GET) works for the following endpoints and 
methods:

- /rules/recipe/(recipeURI) . . . POST
- /rules/recipe/(recipeURI) . . . GET

CORS access (PUT, DELETE, POST, GET) does *not* work for the following 
endpoints and methods:

- /rules/recipe/(recipeURI) . . . PUT
- /rules/recipe/(recipeURI) . . . DELETE
- /rules/recipe/(recipeURI)?rule=(ruleName) . . . DELETE
- /rules/find/rules?name=(ruleName) bzw. 
rules/find/rules?description=(description) . . . GET
- /rules/find/recipes?description=(description) . . . GET

I have not tried yet for:
- /rules/adapters/    # for exporting in other formats such as SWRL and SPARQL 
Construct
- /rules/adapters/recipe
- /refactor    # uses a stored recipe. we should move this to /rules/refactor
- /refactor/apply    # uses a recipe supplied in the request payload
- /refactor/applyfile

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to