Hi there,
I'm writing to follow up on the 403 error we're encountering when calling Jira APIs. The error appears to be CloudFront-related rather than directly from Jira:
`<!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: EOQ1QpDQmuclFI8CWajoUIeuGbZI8mcTkbeuolgGZR8v8W6KM_XKow==\n</PRE>\n<ADDRESS>\n</ADDRESS>\n</BODY></HTML>`
Interestingly, the same API calls work perfectly in Postman with identical details.
Based on the error, this could be due to:
- Request headers mismatch
- User-agent filtering
- IP restrictions
- Rate limiting
Could someone from the Jira team help investigate why our calls are being blocked by CloudFront while Postman succeeds? We're happy to provide additional details about our implementation if needed.
Thanks in advance,
Anupam Dungdung
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.