Created attachment 628406 [details] 3ScreenshotsTrackerBugzill4_2issue.png User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20100101 Firefox/12.0 Build ID: 20120420145725 Steps to reproduce: Having successfully set up Pivotal Tracker http://www.pivotaltracker.com integrations with Bugzilla landfill sandboxes for all versions from 3.6 upwards, cannot with 4.2.1. 1. If you do not have a Tracker login, sign up here: http://www.pivotaltracker.com 2. Create a new project 3. Setup 2 integrations, one with the Bugzilla 4.0 and 4.2.1 landfill sandboxes following these instructions: https://www.pivotaltracker.com/help/integrations?version=v3#bugzilla for comparison of a successful integration with 4.0 vs an unsuccessful one with 4.2 Screenshots show the test setup. I'm a Pivotal Labs employee on the Tracker team. Several customers have reported this and 3 of us are unable to find any information in our logs, or anything else through troubleshooting to point to the problem. Actual results: In Pivotal Tracker, in the project that has been integrated with 4.2, trying to open the Bugzilla Integration panel results in: "Unable to load bugs - Please check your URL and remember to include http://and exclude the xmlrpc.cgi'." when I try to use the column. Expected results: Bugs that match the Search performed by the integration should be loaded in the Bugzilla Integration panel, in Tracker.
I'm pretty sure your problem is that Pivotal Tracker calls xmlrpc.cgi without setting the Content-Type header to text/xml or application/xml, which are now the only two accepted values for this header. If you pass text/plain, it will be rejected for security reasons, see bug 725663 and http://www.bugzilla.org/security/4.0.4/. Please make sure that Pivotal Tracker sets the Content-Type header correctly. If that's the case and the problem still occurs, feel free to reopen this bug.
Assignee: general → webservice
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Component: Bugzilla-General → WebService
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.