Known issues when using Jira and IBM's WebSeal
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
As an admin, you may face problems while setting up your WebSeal configuration for Proxy. While this article will not go in-depth into its configuration, we'll list some of the issues reported and will maintain it with new findings, when applicable.
Atlassian applications allow the use of reverse proxies with our products; however, Atlassian Support does not provide assistance for configuring them. Consequently, Atlassiancannot guarantee providing any support for them.
If assistance with configuration is required, please raise a question on Atlassian Community or engage the vendor responsible for the product.
Solution
1. Content cache control
We have found that the content caching feature of WebSeal is the component that checks the Last-Modified header, and is dependent on it to determine whether to refresh or serve cached content. (From the Jira point of view, this header is not used, and other applications might handle an invalid timestamp more gracefully, if arbitrarily.)
We have found that disabling the content caching feature of the WebSeal proxy can resolve this problem. While the actual implementation is out of scope, this document may help you:
On the same subject, we've created the following bug report and Feature request, respectively:
2. UNEXPECTED_RESPONSE received when configuring application links
This is already fixed on all versions post Jira 8.10.1:
3. Jira Support for HTTP/2
We had reports of the case-insensitive header for HTTP 1.1 causing issues. HTTP/2 requires all headers to be lower-case which has been made possible on Jira 8.13.
Was this helpful?