JIRA and IIS as Reverse Proxy with Reverse rewrite host in response headers option Enabled fails for HTTPS
プラットフォームについて: Server と Data Center のみ - この記事は、サーバーおよびデータセンター プラットフォームのアトラシアン製品にのみ適用されます。
Please note, that Reverse Proxy Configurations are not formally supported by Atlassian. See: Atlassian Support Offerings and Integrating JIRA with IIS for further guidance on IIS Reverse Proxy configuration.
When using IIS as a Reverse Proxy for JIRA, if the option to set
Reverse rewrite host in response headers is enabled, HTTP paths are not changed to HTTPS URL's. This causes browsers to fail loading content.
- JIRA with IIS configured as a Reverse Proxy
Using a Browser with debugging capabilities, reports the Errors such as the following:
This request has been blocked; The content must be served over HTTPS
The Setting to "Reverse rewrite host in response headers" controls whether or not IIS will change the host the client is using to access JIRA. This can be useful when proxying an internal hostname, but complicates HTTPS Reverse proxy access.
Disable the option: "Reverse rewrite host in response headers" may assist with this issue.