[STANBOL-712] CORS access to the Rules endpoint

• Type: Wish
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Rules
• Assignee: Unassigned
• Reporter: Melanie Reiplinger
• Created: 01/Aug/12 13:15
• Updated: 22/Aug/12 14:37

Description

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

Issue Links

• Is contained by: STANBOL-105 Support Multi-Site Scripting via Cross-Origin Resource Sharing