Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

CORS FAiled Warning in Jira

Receiving below Warning in Jira


2020-07-02 04:29:28,641 http-nio-8080-exec-10 WARN  /rest/webResources/1.0/resources [] Additional XSRF checks failed for request: , origin: , referrer: , credentials in request: false , allowed via CORS: false


Base Url is


Why did XSRF checks fail?

What changes needs to be done to fix this?


1 answer

In the logs you can see that the request is using https but the origin is on http


This looks like a miss configuration in your server.xml file.


Have you perform some recent upgrade? I'm asking because server.xml file is usually overwritten during the upgrade process.

If you are running behind a proxy, can you check if the Connector attribute under your server.xml contains the below attributes:

proxyName="" proxyPort="443" scheme="https" secure="true"


See below a Confluence KB that describe the same issue:

Thanks ,

But I checked server.xml multiple types.

We set it correctly. 

Is there any other place, where I can check where origin and referrer is set.

Why it says origin is http



Hi Deepak,

You can find more details here:

In case you modify the server.xml you will need to restart the application in order to apply the changes.

When did this start to happen? 

We started getting it recently.

Not sure the exact reason

I think if you checked the server.xml file and it's correct you should look into Atlassian support channel. Another good practice is redirect http traffic to https on your proxy, maybe it's allowing http as well?

Also I work as consultant at e-Core and we have the expertise to assist you troubleshoot this issue, if that interest  please contact me at and I'll redirect your request internally.

Hi @Deepak Mammen ,

How is your troubleshooting going? Any progress with this issue?

you may try to add to the Allowlist
IF that's OK. means someone use not https to access.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

Why everyone using Jira must be GDPR-compliant

Did you know that penalties up to 4 % of the yearly company turnover are possible in case of GDPR violations? GDPR regulations are currently mainly relevant for companies in the EU, but countries lik...

70 views 1 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you