Endpoint inconsistencies
Matthew Graham
mjg at cacr.caltech.edu
Tue Dec 2 20:27:02 CET 2014
Hi,
There are inconsistencies in the VOSpace 2.0/2.1 spec between the endpoints for transfer details at least for pullFromVoSpace. It is unclear whether the resource is called: details or transferDetails:
>If the transfer was initiated with a HTTP POST to http://rest-endpoint/sync then the response is:
A HTTP 303 status code with the Location header keyword assigned to the endpoint: http://rest-endpoint/transfers/(jobid)/results/transferDetails.
In the example:
<ns0:results xmlns:ns0="http://www.ivoa.net/xml/UWS/v1.0">
<ns0:result xmlns:ns1="http://www.w3.org/1999/xlink" id="transferDetails"
ns1:href="http://localhost:8000/transfers/83c19a500b1c48108d631f1aa020e8bb/results/details"/>
</ns0:results>
The final negotiated details of the transfer can then be retrieved from the URL reported in the result element:
> curl -v "http://localhost:8000/transfers/83c19a500b1c48108d631f1aa020e8bb/results/details"
Cheers,
Matthew
More information about the grid
mailing list