Bug 779049 (SOA-1458) - HttpRouter fire java.lang.IllegalArgumentException if the Status Code is 304 (Not Modified)
Summary: HttpRouter fire java.lang.IllegalArgumentException if the Status Code is 304 ...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1458
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.3 CP01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 CP02
Assignee: Kevin Conner
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-21 11:46 UTC by Magesh Bojan
Modified: 2009-09-29 03:19 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-25 15:32:44 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 779029 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Issue Tracker SOA-1458 0 None None None Never

Internal Links: 779029

Description Magesh Bojan 2009-08-21 11:46:24 UTC 
Date of First Response: 2009-09-16 11:13:56
project_key: SOA
Comment 1 Magesh Bojan 2009-08-21 11:47:01 UTC 
Link: Added: This issue incorporates JBESB-2797
Comment 2 Kevin Conner 2009-09-09 11:39:50 UTC 
Link: Removed: This issue incorporates JBESB-2797
Comment 3 Kevin Conner 2009-09-09 11:40:02 UTC 
Link: Added: This issue depends JBESB-2821
Comment 4 Julian Coleman 2009-09-16 15:06:25 UTC 
Link: Added: This issue related SOA-1441
Comment 5 Julian Coleman 2009-09-16 15:13:56 UTC 
This was done in time for CP02 CR4.
Comment 6 Kevin Conner 2009-09-25 15:32:44 UTC 
Verified present in CR4 release.
Comment 7 Dana Mison 2009-09-29 03:19:03 UTC 
added to 4.3.CP02 release notes as resolved:

GET requests using the If-Modified-Since header could cause HttpRouter to throw an Illegal Argument Exception.  If the requested document had not been modified, then the response would have the status code of 304 and no message body.  HttpRouter was not checking if the message body was empty.  HttpRouter now performs this check and "Status Code 304" responses no longer result in an exception being thrown.
Note You need to log in before you can comment on or make changes to this bug.