Getting 302 Response Code while doing a Httppost in RRC(Software version CLM 6.0) in order to upload an artifact.
I am trying to do a HttpPost in RRC (Software version CLM 6.0) in order to upload an artifact using the below query but i am getting the response code as 302-Found: https://localhost:9443/rm/folders/_28xhUUrsEeW4COkzyIwAGA?postWrappedResource&artifactType=https%3A%2F%2Flocalhost:9443%2Frm%2Ftypes%2F_GLwh0Tp3EeWh5PGTptPpYQ&title=1.docx&description=&private=true&resourceContext=https%3A%2F%2Flocalhost:9443%2Frm%2Fprocess%2Fproject-areas%2F_E87XMjp3EeWh5PGTptPpYQ&vvc.configuration=https%3A%2F%2Flocalhost:9443%2Frm%2Fcm%2Fstream%2F_FH87cDp3EeWh5PGTptPpYQ The expected Response code is 201 Can anyone help me with this? |
One answer
It does not seem that you are using it correctly.
If you're trying to create a requirement artifact using a POST operation with the RM OSLC API, the URL that you used is definitely wrong. Check out the below article and follow the instructions. https://jazz.net/library/article/1197 If you're trying to "upload" a Word document (1.docx ?) and extract the rerquirements, that will be an "import" operation, not "create". I don't think you can achieve this via OSLC using any of the published API. If you're trying to "upload" a Word document as an attachment, again, I am not aware of any published API that can achieve this. Comments
Prachi Arora
commented Aug 31 '15, 1:15 a.m.
Hi Donald,
Thanks for your response.
I don't want to create a new artifact . I am trying to upload an artifact i.e.,1.docx which is present locally in some folder on my system to a folder in RRC, I was able to do it using the query that I mentioned above in CLM 5.0 but after the change in the CLM version to 6.0 it is somehow not working.
Donald Nong
commented Aug 31 '15, 6:02 a.m.
I don't know how you can do it with CLM 5.0 as this is not a published API. Internal APIs (not published) can change significantly between versions.
|
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.