JIRA and IIS as Reverse Proxy with Reverse rewrite host in response headers option Enabled fails for HTTPS

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

この記事はアトラシアンのサーバー製品にのみ適用されます。クラウドとサーバー製品の違いについてはこちらをご確認ください。

 

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.

最終更新日: 2016 年 2 月 26 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.