Hi,
We are currently experiencing issues getting ticket information using the Jira get requests in our application. The issue seems to be intermittent. We have been using the request logic and query parameters for quite some time and nothing has changed. Just wondering if there are any issues going on the CloudFront side? And when can we expect for this to get resolved?
We get the Error 403 response as follows:
{"statusCode":403,"body":"<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<HTML><HEAD><META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\n<TITLE>ERROR: The request could not be satisfied</TITLE>\n</HEAD><BODY>\n<H1>403 ERROR</H1>\n<H2>The request could not be satisfied.</H2>\n<HR noshade size=\"1px\">\nBad request.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n<PRE>\nGenerated by cloudfront (CloudFront)\nRequest ID: dKrWGTPrX0znpxHqi5290cJU1uCl4mgW_U2MCXr3IEojIpzEirYFQA==\n</PRE>\n<ADDRESS>\n</ADDRESS>\n</BODY> ...
@Anmol Singh which API endpoint are you using? Also maybe provide an example of how you are calling the Jira API - it would help to debug this further.
Hi Richard, we are using the following:
var issueKey = msg.topic;
var callback = function(errors, response, body) {
if (errors) {
console.log("Error processing search. " + JSON.stringify(errors));
} else if (response.statusCode === 200) {
msg[property_key] = response.body.key;
msg[property_body] = response.body
console.log(msg);
} else {
text: "Get failed"
});
console.log("Error getting issue (" + response.statusCode + "): " + JSON.stringify(response));
}
};
server.get(issueKey, callback);
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Richard,
We are still facing the same issue. Request id - M0w1tHNcqKdUBCevCj-1w9ObVnndlkRCu99jsc40S-Pb5dTUtBm-yw
The server.get method uses the following options:
var options = {
rejectUnauthorized: false,
uri: decodeURIComponent(url + 'issue/' + issueKey),
method: 'GET',
followAllRedirects: true,
json: true
};
node.doRequest(options, callback);
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.