[
https://issues.apache.org/jira/browse/CXF-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570343#comment-13570343
]
Benson Margulies commented on CXF-4805:
---------------------------------------
How does this prevent OPTIONS transaction from being processed by the
subsequent interceptors?
> SOAP services try to process HTTP 'OPTIONS'
> -------------------------------------------
>
> Key: CXF-4805
> URL: https://issues.apache.org/jira/browse/CXF-4805
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.5.6
> Reporter: Benson Margulies
>
> We tried, somewhat absentmindedly, to access a JAX-WS SOAP service
> cross-origin-ly from a browser. The browser sent the required OPTIONS ahead
> of the POST, and CXF went ahead and tried to handle it as if it was a SOAP
> request, and then got very sad trying to parse the empty payload as XML.
> Shouldn't CXF have produced a clear log message and error response about not
> understanding OPTIONS?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
