Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Mon, 4 Feb 2013 15:50:17 +0000 (UTC)
From: "Benson Margulies (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12630634.1359983445380.239900.1359993017588@arcas>
In-Reply-To: <JIRA.12630634.1359983445380@arcas>
References: <JIRA.12630634.1359983445380@arcas>
Subject: [jira] [Commented] (CXF-4805) SOAP services try to process HTTP
 'OPTIONS'
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ 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