You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 21, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.The text was updated successfully, but these errors were encountered: