403 Forbidden Related to /secure/projectavatar

Our logs see about 50-100 of these per hour in our web logs. The path, appended to the base url, actually goes straight to Atlassians 404 skull/crossbones page.

My ultimate question: Can we ignore it?

1 answer

1 accepted

most possible that is one disconnected jira with unlogged user in some browser tries to update activity stream (we had the similar traffic, but not exact match). Check the ip address of the requests, maybe you will find machine in your office / home

Thanks Alexey - yes that makes sense. The page remains open and the ajax tries to update the activity stream after the authentication timeout.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Jira

5 ways you can make the most of Jira Software and Bitbucket Cloud

As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...

56 views 0 5
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you