[Walrus] Incorrect response for ranged GET
Bug #729054 reported by
Gilles Gaillard
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Eucalyptus |
Fix Committed
|
Undecided
|
Neil Soman | ||
2.0 |
In Progress
|
Undecided
|
Unassigned |
Bug Description
1. As per RFC-2616 14.35.1 when a byte range is submitted in a GET the "last-byte-pos value gives the byte-offset of the last byte in the range". Eucalyptus instead returns one byte less than expected. It seems to me that the issue is in FileSystemStora
2. Still as per the same reference, the server SHOULD return a response with a status of 206 (Partial Content) instead of 200 (OK).
Related branches
Changed in eucalyptus: | |
assignee: | nobody → Neil Soman (neilsoman) |
To post a comment you must log in.
Also per the same RFC, specifying an incomplete range like:
Range: bytes=567889-
should be accepted.
Currently it returns a 500 'Internal error' which is reflected in logs by: ing:New I/O server worker #1-4] ERROR java.lang. ArrayIndexOutOf BoundsException : 1 ArrayIndexOutOf BoundsException : 1 ws.handlers. WalrusRESTBindi ng.parseExtende dHeaders( WalrusRESTBindi ng.java: 730) ws.handlers. WalrusRESTBindi ng.getOperation (WalrusRESTBind ing.java: 580) ws.handlers. WalrusRESTBindi ng.bind( WalrusRESTBindi ng.java: 285) ws.handlers. WalrusRESTBindi ng.incomingMess age(WalrusRESTB inding. java:180) ws.handlers. WalrusRESTBindi ng.handleUpstre am(WalrusRESTBi nding.java: 158)
14:59:12 [WalrusRESTBind
java.lang.
at com.eucalyptus.
at com.eucalyptus.
at com.eucalyptus.
at com.eucalyptus.
at com.eucalyptus.