cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ka-Lok Fung (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CXF-3530) Performing an OPTIONS on a JAX-RS subresource causes CXF to generate a 405 status instead of a 200 status
Date Wed, 18 May 2011 01:25:47 GMT

     [ https://issues.apache.org/jira/browse/CXF-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ka-Lok Fung updated CXF-3530:
-----------------------------

    Summary: Performing an OPTIONS on a JAX-RS subresource causes CXF to generate a 405 status
instead of a 200 status  (was: OPTIONing a JAX-RS subresource causes CXF to generate a 405
status instead of a 200 status)

> Performing an OPTIONS on a JAX-RS subresource causes CXF to generate a 405 status instead
of a 200 status
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-3530
>                 URL: https://issues.apache.org/jira/browse/CXF-3530
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.4, 2.3.4
>         Environment: JDK 1.6
>            Reporter: Ka-Lok Fung
>             Fix For: 2.4.1, 2.3.5
>
>         Attachments: cxf.subresource.options.trunk.diff
>
>
> If you OPTIONS the subresource of a JAX-RS resource, CXF's JAX-RS implementation returns
405 instead of 200.
> If you OPTIONS a JAX-RS resource directly, CXF generates a 200.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message