Walrus partial get returns a wrong response code

I have changed the package selection to eucalyptus.

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

Hi there-

Eucalyptus-1.5.2 is several versions back-level now.

Any chance you can reproduce this on eucalyptus 1.6.2 in Lucid?

Hi,

I will install lucid into my local machine during the week end, and see if returns the right code.
Thanks

Nicola

Hi all,

I installed lucid and setup eucalyptus (walrus-1.6.2-0ubuntu25). The return code is still wrong.

In order to get the wrong error code I used the following command:

curl -H "Date: Sun, 28 Mar 2010 11:43:23RcZy5anTxlg:7EBdJdhY3CoJxrIG6eCouAPIyHk=" -L -H "content-type:" -r 0-200 -s -v http://192.168.1.69:8773/services/Walrus/ns/README

and the return msg is:

* About to connect() to 192.168.1.69 port 8773 (#0)
* Trying 192.168.1.69... connected
* Connected to 192.168.1.69 (192.168.1.69) port 8773 (#0)
> GET /services/Walrus/ns/README HTTP/1.1
> Range: bytes=0-200
> User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15
> Host: 192.168.1.69:8773
> Accept: */*
> Date: Sun, 28 Mar 2010 11:43:23 +0000
> Authorization: AWS NyoQIMdSyMH8vaRLStAUcNistFdRcZy5anTxlg:7EBdJdhY3CoJxrIG6eCouAPIyHk=
>
< HTTP/1.1 200 OK
< Content-Length: 200
< Content-Range: 0-200/2572
< Content-Type: binary/octet-stream
< ETag: 525e3eb8ad5a75e241ea68ef3ce835d1
< Last-Modified: 2010-03-28T11:23:31.000+0000

as you can see the code is still 200 instead of 206. This represents a problem with libraries like jets3t which are checking if the partial get returns the correct code.
Thanks

Nicola

[Expired for eucalyptus (Ubuntu) because there has been no activity for 60 days.]