The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Why getting redirect exceed 30 error while creating JIRA ticket with REST API

Aleena
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 19, 2017

I was creating jira tickets with REST API, but facing  "redirect exceed 30" error. It was working fine for few months. But suddenly seeing this fail.

the server name I was using is 'https://jira.abc.com"

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Andy Heinzer
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
December 22, 2017

I haven't been able to find much on this error as to how it might directly relate to Atlassian APIs.  But I did find on explanation of this kind of error over in this stackoverflow post:  https://stackoverflow.com/questions/42237672/python-toomanyredirects-exceeded-30-redirects

So that seems to indicate that the request you are making looks like it's getting caught in some kind of redirect loop forever.  And rather than let the request go on like that forever, it has an upper limit on the number of redirects before it fails.

I would be interested to learn more about how you are generating this specific REST call.  I'm curious of how you are doing this?  Are you using cUrl to make the call, or postman, or some other application?   Just wanted to see if there might be something wrong with the syntax of your request that might be contributing to this odd error.  I can foresee a scenario in regards to a malformed request that could be getting caught in this kind of loop.

TAGS
AUG Leaders

Atlassian Community Events