Bug 958896
Summary: | RESTEasy: Invalid Content-Type in response - Bad behavior when invalid accept header is specified in request header | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | agalad |
Component: | RESTEasy | Assignee: | Weinan Li <weli> |
Status: | CLOSED UPSTREAM | QA Contact: | Nobody <nobody> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.1.0 | CC: | myarboro, nobody, olukas, pslavice |
Target Milestone: | ER6 | ||
Target Release: | EAP 6.1.0 | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
There exists a problem within the RESTEasy subsystem of JBoss EAP 6 where an incorrect `HTTP 200` response is sent when there is an invalid accept header in a received HTTP request.
When an invalid accept header is provided, the correct response should be `HTTP 500`. This issue is currently under investigation.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-06-18 07:54:25 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
agalad
2013-05-02 15:41:06 UTC
Verified that RESTEasy 3.0.5.Final fixed this issue. Do we have to fix this in Branch_2_3? I propose we mark it as "won't fix". EAP7 + RESTEasy 3.x will fix this problem. |