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?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.