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
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,488 views 15 20
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