You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Mike Kelly (Jira)" <ji...@apache.org> on 2019/11/12 18:32:00 UTC
[jira] [Created] (CXF-8154) No "Reason Phrase" Sent with HTTP
Responses
Mike Kelly created CXF-8154:
-------------------------------
Summary: No "Reason Phrase" Sent with HTTP Responses
Key: CXF-8154
URL: https://issues.apache.org/jira/browse/CXF-8154
Project: CXF
Issue Type: Bug
Components: JAX-RS
Affects Versions: 3.3.4
Environment: Apache Tomcat 8.5, OpenJDK 1.8
Reporter: Mike Kelly
When I throw, for example, a {{javax.ws.rs.NotFoundException}}, my expectation is that the response would start with a Status Line like:
{noformat}
HTTP/1.1 404 Not Found
{noformat}
However, I just get a response like:
{noformat}
HTTP/1.1 404
{noformat}
This seems to be true both if I provide a {{message}} when I construct the exception, or if I use the no argument constructor.
This is similarly true for any exceptions triggered internally by CXF, for example if I make a request with an unsupported method. The stack trace in my logs shows a {{javax.ws.rs.ClientErrorException: HTTP 406 Not Acceptable}}, but the response just shows {{HTTP/1.1 406}}.
My expectation is that either the appropriate default "reason phrase", or the {{message}} I provided to my constructed exception, would be returned to the caller?
My reading of RFC 2616 is that such a reason phrase is not optional: https://tools.ietf.org/html/rfc2616#section-6.1
--
This message was sent by Atlassian Jira
(v8.3.4#803005)