Rally: "Parser is unable to parse the response" and 400 HTTP error when trying to delete a story or a feature
Article ID: 188143
Updated On:
Products
Rally SaaS
Rally On-Premise
Issue/Introduction
When users click on "delete" on a story/feature, the following error message appears in Rally UI: "Parser is unable to parse the response". These users have editor or even Project admin rights to the team where the item is, and no other dependencies are present that would prevent this function.
Subscription admins are able to perform the deletion without an issue.
The browser console shows: "Failed to load resource: the server responded with a status of 400 (Bad Request)" for the DELETE Request method
The Response of the DELETE Request Method is:
<html>
<head><title>400 Bad Request</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<hr><center>cloudflare</center>
</body>
</html>
<!-- a padding to disable MSIE and Chrome friendly error page -->
Subscription admins are able to perform the deletion without an issue.
The browser console shows: "Failed to load resource: the server responded with a status of 400 (Bad Request)" for the DELETE Request method
The Response of the DELETE Request Method is:
<html>
<head><title>400 Bad Request</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<hr><center>cloudflare</center>
</body>
</html>
<!-- a padding to disable MSIE and Chrome friendly error page -->
Environment
Release : SAAS
Component : AGILE CENTRAL
Cause
Firewall/network configuration
Resolution
Configure network/firewall to avoid rejecting DELETE Request Method for certain users.
Workaround: Delete more than one item at a time. This action will perform a POST Request Method instead of DELETE, allowing the user to delete the stories/features.
Workaround: Delete more than one item at a time. This action will perform a POST Request Method instead of DELETE, allowing the user to delete the stories/features.
Feedback
Yes
No
Powered by
