Tomcat で特定の URL へのアクセスをブロックする方法
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
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.
*Fisheye および Crucible は除く
このページの内容はサポート対象外のプラットフォームに関連しています。したがって、アトラシアン サポートではこのページの記載内容のサポートの提供は保証されません。この資料は情報提供のみを目的として提供されています。内容はお客様自身の責任でご利用ください。
目的
In some cases, you may wish to restrict access to a specific URL within your Atlassian Applications - for example, if clients are accessing a URL that causes load on the application server. If you don't have access to the reverse proxy (or are not using a reverse proxy) you can modify Tomcat directly.
This solution is only applicable for Atlassian Applications that run under Apache Tomcat - such as Jira, Confluence, Crowd.
ソリューション
- Shut down the application
- backup your $application-install/atlassian-jira/WEB-INF/web.xml file
- Modify the web.xml file with a text editor of your choice and locate this comment element at the end:
<!--
All session-config, mime-mapping, welcome-file-list, error-page, taglib,
resource-ref, security-constraint, login-config, security-role,
env-entry, and ejb-ref elements should follow this fragment.
-->
- On your Jira instance, Navigate to the page that you would like to block and copy the URL.
- Remove the Base URL and replace the contents of the <url-pattern> element.
- Note that the context path should not be in the <url-pattern>. Multiple <url-pattern> elements can be added. For URL's with parameters, the wildcard is not used.
- Add the following block after the comment block and inside the <web-app> element(Before the </web-app>:
<security-constraint>
<web-resource-collection>
<url-pattern>/path/to/block/without/context/root/*</url-pattern>
<http-method>GET</http-method>
</web-resource-collection>
<auth-constraint />
</security-constraint>- Start your application
- If you are running a Data Center with multiple nodes, you will need to repeat the steps above on all nodes.