Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,461,945
Community Members
 
Community Events
176
Community Groups

Error response when contacting REST API using LocalHost

Trying to use the Jira REST API to parse data from tickets in my company. When making Get requests through Postman to refine my jql searches, everything works fine and the ticket information is returned successfully.  When trying to use the same queries through TypeScript on a LocalHost webserver, it returns an error.

Here is the request in the TypeScript file, using the Axios library to parse API requests:

const result = await axios.get(`${token}@Content-Type:application/json/https://${siteName}.atlassian.net/rest/api/latest/issue/${key}-${number}`)

Here is the error that is returned in browser. For my tests, I used Google Chrome:

Access to XMLHttpRequest at 'xxxx' from origin 'https://localhost:3000' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, chrome-untrusted, https.

So it seems to be blocking the request because it comes from an unsecured URL despite it containing https protocol. Is there a way to get these requests to go through, barring a fully published release of the web tool that is being developed?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events