Bug 817275 - Setting the ResourceResponse.HTTP_STATUS_CODE property does not modify the actual server response status code
Summary: Setting the ResourceResponse.HTTP_STATUS_CODE property does not modify the ac...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 5
Classification: JBoss
Component: distribution
Version: 5.1.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Christopher O'Brien
QA Contact: Len DiMaggio
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-28 14:30 UTC by dpardon
Modified: 2016-08-02 16:04 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-02 16:04:39 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description dpardon 2012-04-28 14:30:09 UTC 
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.