How to block Activity Stream on the HTTP proxy

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

The content on this page relates to platforms which are not supported. Consequently, Atlassian Support cannot guarantee providing any support for it. Please be aware that this material is provided for your information only and using it is done so at your own risk.

To prevent users from JIRA from viewing activity streams from another JIRA ( with public access ) which is integrated with application link.

Solution

  • Blocking the activity stream on the HTTP proxy

  • This is the the nginx configuration used :

    1 2 location /plugins/servlet/streams { return 200; }
Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.