CS: Query path for storage/access statistics appears wrong?

Toby Corkindale toby at dryft.net
Wed Jul 2 22:04:17 EDT 2014

On 3 July 2014 01:57, Hector Castro <hector at basho.com> wrote:
> Hey Toby,
> Are you authenticating the request that uses query string parameters?

Hi Hector,
In both cases I am authenticating the request, using the AWS header method.
I noted that I needed to only do the auth hash based on the path, not
the query parameters, in order for it to succeed though. I just
assumed that was intentional as the AWS spec does indicate that too.

> On Wed, Jul 2, 2014 at 1:23 AM, Toby Corkindale <toby at dryft.net> wrote:
>> Hi,
>> Maybe I'm doing something wrong, but I find I can only access the Riak
>> CS storage/access information per-user by using the s3-compatible
>> path, not the REST API path -- even though I am connecting to the REST
>> API port.
>> ie. To get the statistics, I am querying
>> http://SERVERNAME:8080/riak-cs/usage/USER-ID/b/STIME/ETIME
>> An actual URI generated this way would be:
>> /riak-cs/usage/ZAZ6_VYSIE7QMYQRRHY3/b/20140528T000000Z/20140602T000000Z
>> If I try to use the proper API method, I consistently receive
>> "not_requested" as the results.
>> The API URL is:
>> http://SERVERNAME:8080/riak-cs/usage/USER-ID?b&e=ETIME&s=STIME
>> An actual URI generated this way would be:
>> /riak-cs/usage/JEJ-XPZBSIKSU_Z4EGPC?b&e=20140602T000000Z&s=20140528T000000Z
>> Is this a known bug or should this be working (and I'm just doing it wrong?).
>> Current latest stable Riak - 1.4.9-1 from Basho Ubuntu repo.
>> Cheers,
>> Toby
>> _______________________________________________
>> riak-users mailing list
>> riak-users at lists.basho.com
>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Turning and turning in the widening gyre
The falcon cannot hear the falconer
Things fall apart; the center cannot hold
Mere anarchy is loosed upon the world

More information about the riak-users mailing list