[
https://issues.apache.org/jira/browse/CXF-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Beryozkin resolved CXF-3897.
-----------------------------------
Resolution: Won't Fix
Assignee: Sergey Beryozkin
I realized we also can have queries such as _type=text/xml, in other words,
having no shortcut for _type is not a bug
> Better handling on invalid JAXRS '_type' parameter
> --------------------------------------------------
>
> Key: CXF-3897
> URL: https://issues.apache.org/jira/browse/CXF-3897
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.3.7, 2.4.3, 2.5
> Reporter: Woonsan Ko
> Assignee: Sergey Beryozkin
> Priority: Minor
> Fix For: 2.3.8, 2.4.5, 2.5.1
>
> Attachments: CXF-3897.patch
>
>
> From the discussion on the user list:
> > From: Sergey Beryozkin <[email protected]>
> > To: [email protected]
> > Cc:
> > Sent: Tuesday, November 8, 2011 4:44 PM
> > Subject: Re: No warning on invalid _type parameter
> >
> > Hi
> > On 08/11/11 19:41, Woonsan Ko wrote:
> >> Hi,
> >>
> >> When an undefined _type parameter is used for JAX-RS requests (e.g.,
> > ?_type=foo), it doesn't give any warning logs. It just returns 406 http
> > error code.
> > Enabling the fine logging should tell that no Accept header was matched...
> >> It seems better to give a proper warning log in
> > o.a.cxf.jaxrs.impl.RequestPreprocessor#handleTypeQuery() method in that
> > case.
> >> Also, it currently uses the invalid type as Accept header even though
> > there's no shortcut registered for the type parameter value.
> >
> > Agreed - it's a bug
> >
> >> Shall I create an JIRA issue with a patch for this?
> >>
> > Yes please, thanks
> > Sergey
> >
> >> Kind regards,
> >>
> >> Woonsan
> >
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
