RQM Feeds returned as HTML instead of XML
![]() Hi, We have develop a Utility which publish existing automation tools testcase to RQM. The utility works great on some servers but not with others. On some of the servers when requesting a feed (Example: https://bajazz02:9675/qm/service/com.ibm.rqm.integration.service.IIntegrationService/projects) we receiving an HTML page instead of the expected XML. The returned Html page main content is a message indicating "loading..." What should I look for in order to either resolve this issue and/or help me debug the problem. Here are some of the things I have already verified 1. All servers are using form and not base for authentication 2. The utility http header contains the Accept = application/xml and the Content-Type = application/xml |
4 answers
![]()
Marc,
Are you using Poster in conjunction with Firefox? If so, try logging into the QM project before attempting to use Poster so that a session has been established
Also, sure to also include your user credentials as a part of the request when using Poster
![]() Comments Hi Ara,
|
![]()
Hi,
Thank you for everyone for helping on this issue! Here was the resolution of the problem: Turns out that the working RQM server where using Websphere 8 and the ones not working where using WebSphere 7. The admin server applied an FP and it started to work. We suspect that one of the following PM was the root cause of the problem PM84259 Prevent adding WASReqURL cookie when login page is protected.
WASReqURL cookie might no longer be deleted after login
Comments NOTE: I was encountering the same issue with the Jazz.net server RQM sandbox and it may be a good ideal to investigate it
|
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.
Comments
Hi Marc,
Can you install and start Firebug and then load the page? What are the errors which firebug displays?
HI Krzysztof,
No error displayed in Firebug. Note: The error does not occur when using a browser, it only happens when using our utility Http client connection