Confluence 6.0 does not load properly behind Microsoft's Web Application 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
Atlassian applications allow the use of reverse-proxies within our products, however Atlassian Support does not provide assistance for configuring them. Consequently, Atlassian can not guarantee providing any support for them.
If assistance with configuration is required, please raise a question on Atlassian Community.
Problem
Confluence 6.0 does not load properly behind Microsoft's Web Application proxy, even with Collaborative Editing disabled. Microsoft's Web Application Proxy cannot be used with Collaborative Editing as it does not support web sockets, which are required to use Collaborative Editing.
You may see 404 or 400 error requests in a HAR output while loading the Confluence page for resources like: GET atlassian-icons.woff and GET atlassian-icons.ttf.
Cause
Some Microsoft Web Application Proxy configurations may be affected by WAPs encoding of certain URLS.
Resolution
Install the Hotfix from Microsoft: Hotfix 3042127: "HTTP 400 - Bad Request" error when you open a shared mailbox through WAP in Windows Server 2012 R2.
⚠️ This will allow you to use Microsoft's Web Application proxy with Confluence 6.0, but note that it will still not allow you to implement Collaborative Editing.
Was this helpful?