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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

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

Atlassian Community Events