You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Yoshani Ranaweera (Jira)" <ji...@apache.org> on 2024/02/06 04:15:00 UTC

[jira] [Commented] (CXF-8972) Server exception raised when no Content-Type param provided

    [ https://issues.apache.org/jira/browse/CXF-8972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814594#comment-17814594 ] 

Yoshani Ranaweera commented on CXF-8972:
----------------------------------------

[~reta] the end-user experience I see here is that when the client misses the optional Content-Type header param, regardless of the actual body content, a server exception is raised and logged. Is this expected?

> Server exception raised when no Content-Type param provided
> -----------------------------------------------------------
>
>                 Key: CXF-8972
>                 URL: https://issues.apache.org/jira/browse/CXF-8972
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>            Reporter: Yoshani Ranaweera
>            Priority: Major
>
> If a request is sent without the Content-Type header parameter, a server exception _javax.ws.rs.WebApplicationException: HTTP 415 Unsupported Media Type_ is raised [1] and the below server error log is printed. 
> _{org.apache.cxf.jaxrs.utils.JAXRSUtils} - No message body reader has been found for class java.lang.String, ContentType: application/octet-stream_
> Since this is a client error, it should not be handled as a server exception. 
> [1] [https://github.com/apache/cxf/blob/main/rt/frontend/jaxrs/src/main/java/org/apache/cxf/jaxrs/utils/JAXRSUtils.java#L1581]
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)