Skip to content
This repository was archived by the owner on Jan 21, 2024. It is now read-only.

Allow OPTIONS request on the <xe:restService> component #20

Open
markleusink opened this issue Apr 8, 2015 · 1 comment
Open

Allow OPTIONS request on the <xe:restService> component #20

markleusink opened this issue Apr 8, 2015 · 1 comment

Comments

@markleusink
Copy link

If the <xe:restService> control receives an OPTIONS request (which is kind of standard when doing REST), it immediately throws a 405 HTTP error. See also http://stackoverflow.com/questions/29478188/domino-cors-and-the-options-request. Would be great if the relevant classes could be changed to allow that: it doesn't even need any response, just the correct status code.

@edm00se
Copy link

edm00se commented Feb 22, 2017

It would be good to have that in the xe:restService, although it's probably worth mentioning that this is fully achievable if you implement the xe:restService via implementing a com.ibm.xsp.extlib.component.rest.CustomServiceBean, since you can/do manually check the request method.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants