Closed aparsons closed 9 years ago
Why was this closed?
An excellent question.
It was closed because we think we have actually addressed this issue in recent commits that should be back-ported to the ThreadFix 2.2 stable branch. This discussion was played out in our internal JIRA discussions of open ThreadFix issues and communications about them.
BUT - the reason it was closed without further information being forwarded along your way (which is a completely reasonable thing for you to expect) was that we take all GitHub issues and pipe them to our internal JIRA instance where we manage the actual ThreadFix workload which is based on developers completing features, etc. Comments to those JIRA issues don't get pumped to more public repositories just yet and that is something we need to fix.
SO - I think your issue will have been resolved when some of the most recent updates have been applied. Sorry for any confusion about what folks have been doing
Thanks,
Dan
Additionally, we're looking for a better way for us to push DG-internal comments about an issue out to an external audience. My apologies for any confusion and please work with us to address this issue.
Great. I'll test it on the later code in a bit and if I still see the issue I'll let you guys know.
The set application url api call (rest/applications/[appId]/addUrl) returns a system error HTML document. It does correctly set the url, but I would expect the response to be the application json object.
Documentation: https://github.com/denimgroup/threadfix/wiki/Threadfix-REST-Interface#set-url
Here is a curl example.
Here is the response body.
Here is the error log.