storage.objects.compose Issue

[jonathannorris]

I am attempting to use the storage.object.compose function, but it looks like because it doesn't have a mediaUrl its not sending the body of the request. For all my requests all I am getting as a response is "Not Found". I have tried the same requests on the API Explorer and they work properly.

The format of the params I am passing to storage.object.compose is:

{
    "destinationBucket": "bucket",
    "destinationObject": "jsonPath.json",
    "resource": {
        "kind": "storage#composeRequest",
        "destination": {
            "contentType": "application/json"
        },
        "sourceObjects": [
            {
                "name": "name1.json"
            },
            {
               "name": "name2.json"
            }
        ]
    }
}

[ryanseys]

it looks like because it doesn't have a mediaUrl its not sending the body of the request

There's no media url specified in the docs and API Explorer doesn't support media request anyway, so if you're having no trouble running it on API Explorer, there's no need for a media URL.

Not found suggests that one of the values you're specifying cannot be accessed either because it doesn't exist or because you don't have the right permissions. Have you ensured that all scopes are allowed or you're using a service key and that you've enabled the API on your project?

[jonathannorris]

Figured it out, the issue was I wan't url encoding the params. You might want to consider url encoding any parameters that you internally use in urls.

[ryanseys]

What specific parameters? Can you give an example of what you gave initially and what fixed it? Thanks!

[jonathannorris]

Both the destinationBucket and destinationObject needed to be url encoded because they contained '-' and '.':

var destinationObject = '2014-7-29/20/events_1003152.json';
encodeURIComponent(destinationObject);

I found this behavior odd because I expected the googleapis package would url encode any parameters it is using in a url. Leaving it up to the developer is ok if its explicit, but that requires the developer to figure out what parameters are being used in urls.

[ryanseys]

Yes, I agree, the library should be url encoding these. I'm filing a separate issue for it right now.

For the record, any parameters on the top level (not resource or media) are query parameters that go in the URL, so we will have to url encode all of these.

Thanks again for reporting this.

[ryanseys]

Should be fixed now! :) 👍