HTTP Status Code 410(GONE) when trying to retrieve artifact through REST Client (OLSC API)
I have a few questions that may be related to the same issue:
I currently have a bunch of requirements that are in a global configuration that are within a change set, the change set has not been delivered.
I am using the OSLC API to try and retrieve these artifacts:
when i run this query, I return every artifact within the module:
&componentURI=https://jazz.server.com/rm/cm/component/_xxxxxx
&vvc.configuration=https://jazz.server.com/rm/cm/changeset/_xxxxx
&oslc.select=*
&oslc.prefix=rdf=<http://www.w3.org/1999/02/22-rdf-syntax-ns#>&olsc=<http://open-services.net/ns/core#>>
Which is great but I only need a specific set of modules within a folder, I used the Folder Query to find the corresponding folder that the requirements are in and run a Query using the folder as the parent I get a GONE.ERROR. from the server.
So to investigate further, I went into DNG and navigated to the folder with the requirements, got the URL and posted into my REST client, which returned, a list of all the artifacts with the following structure:
oslc_rm:uses rdf:resource="https://jazz.server.com/rm/resources/XXXXXXXX"
when I copy that URI into the REST Client I get a 410 (GONE)
Has anyone else received a gone status code? Could it somehow be related to the change set not being delivered?
|
One answer
It looks like you have missed the configuration context when doing the GET request for this particular artifact's URI.
You need to set the HTTP header "Configuration-Context: https://jazz.server.com/rm/cm/changeset/_xxxxx"
or append the URL query "oslc_config.context=https://jazz.server.com/rm/cm/changeset/_xxxxx".
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.