When Jira is accessed via the RSA portal, certain functionalities do not work as expected. Users are able to log in, but widgets fail to load, and multiple features are non-functional.

However, when Jira is accessed directly within the local network, it operates normally.

The issue is related to handling long URIs when accessing Jira through the RSA portal or a reverse proxy.

A review of the IDR logs showed no suspicious activity. However, analysis of Apache HTTP Server version 2.4.58 revealed that the mod_substitute module enforces a maximum substitution limit of 5 MB.

Requests containing long URIs are likely exceeding this limit, which results in broken widgets and non-functional features in Jira when accessed via the portal.

As a temporary solution, the customers can increase the maximum line length for substitutions in the Cloud Administration Console.

1. Sign in to Cloud Administration Console.
2. Navigate to Applications > My Applications.
3. Click Edit for the Jira application.
4. Go to Proxy Settings.
5. Click Advanced Configuration.
6. Under Rewrite Rules, add the following rule:
   SubstituteMaxLineLength 10M
7. Save the configuration.
8. Publish the changes.

This change raises the maximum substitution line length to 10 MB, preventing long URI requests from exceeding the default 5 MB limit in mod_substitute.