0

Dave Evans (148●1●28●46) | asked Oct 15 '20, 2:57 p.m. Calling this URL (with OSLC headers) in DOORS works: https://myDOORS/rm/views?oslc.query=true&projectURL=[Project URL]&oslc.prefix=rt=<https://myDOORS/rm/types>&oslc.select=rt:[Custom Attribute Id] But calling this URL returns OK status with an empty response message: https://myRQM/qm/proxy?uri=[URL from above passed through javascript's encodeURIComponent] Can you tell if there a problem/limitation with the RQM proxy service, or what DOORS can send via proxy? Or am I doing something wrong? I do have Global Config Management enabled, and my URL does not specify the config context... but I would expect an error if DOORS can't identify it and needs it. However, maybe getting OSLC from within a DOORS widget is OK, whereas getting OSLC from RQM requires some other upfront info? I can see that the RQM application makes plenty of proxy calls that DO work (such as /qm/proxy?uri=https://myJTS/jts/whoami), and a proxy call to DOORS when I open a requirements picker. Thanks in advance! Comments Dave Evans commented Nov 23 '20, 4:01 p.m. I found out that I needed to do encodeUrl on the portion after proxy?url= However, there still does seem to be some dysfunction in the proxy service, such as this URL I can't get data from: https://DOORS/rm/proxy?uri=https%3A%2F%2FRTCSERVER%2Frpt%2Frepository%2Ffoundation%2Ffields%3DprojectArea%2FprojectArea%2F(name%7CitemId)

One answer

---

Register or log in to post 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.