Bug 817275 - Setting the ResourceResponse.HTTP_STATUS_CODE property does not modify the actual server response status code
Setting the ResourceResponse.HTTP_STATUS_CODE property does not modify the ac...
Status: CLOSED NEXTRELEASE
Product: JBoss Enterprise Application Platform 5
Classification: JBoss
Component: distribution (Show other bugs)
5.1.2
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Christopher O'Brien
Len DiMaggio
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-28 10:30 EDT by dpardon
Modified: 2016-08-02 12:04 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-08-02 12:04:39 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description dpardon 2012-04-28 10:30:09 EDT
Description of problem: Setting the ResourceResponse.HTTP_STATUS_CODE property does not modify the actual server response status code


Version-Release number of selected component (if applicable):


How reproducible:always


Steps to Reproduce:
1.Set the status code from a serveResource Portlet context: resourceResponse.setProperty(ResourceResponse.HTTP_STATUS_CODE,"500")
2.Invoke the above serveResource from a client-side ajax request
3.Inspect the status code received in a web browser console: the web browser always receives a status code "200" .
  
Actual results:"200"


Expected results:"500"
This code works for instance with Gatein 3.2, the expected status code is correctly received on client-side.

Additional info:. It is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=793073, closed 2 years ago.

Note You need to log in before you can comment on or make changes to this bug.