クラウド
Data Center 4.12
バージョン
- 9.5
- 9.4
- 9.3
- 9.2
- 9.1
- 9.0
- 8.19
- 8.18
- 8.17
- 8.16
- 8.15
- 8.14
- 8.13
- 8.12
- 8.11
- 8.10
- 8.9
- 8.8
- 8.7
- 8.6
- 8.5
- 8.4
- 8.3
- 8.2
- 8.1
- 8.0
- 7.21
- 7.20
- 7.18
- 7.19
- 7.17
- 7.16
- 7.15
- 7.14
- 7.13
- 7.12
- 7.11
- 7.10
- 7.9
- 7.8
- 7.7
- 7.6
- 7.5
- 7.4
- 7.3
- 7.2
- 7.1
- 7.0
- 6.10
- 6.9
- 6.8
- 6.7
- 6.6
- 6.5
- 6.4
- 6.3
- 6.2
- 6.1
- 6.0
- 5.16
- 5.15
- 5.14
- 5.13
- 5.12
- 5.11
- 5.10
- 5.9
- 5.8
- 5.7
- 5.6
- 5.5
- 5.4
- 5.3
- 5.2
- 5.1
- 5.0
- 4.14
- 4.13
- 4.12
- すべて表示
Disabling HTTP(S) access to Git repositories in Bitbucket Server
Advanced actions
- Running the Bitbucket Server installer
- Automated setup for Bitbucket Server
- Starting and stopping Bitbucket Server
- Install Bitbucket Server from an archive file
- Install and configure a remote Elasticsearch instance
- Running Bitbucket Server as a Linux service
- Running Bitbucket Server as a Windows service
- Bitbucket Server config properties
- Proxying and securing Bitbucket Server
- Enabling SSH access to Git repositories in Bitbucket Server
- Using diff transcoding in Bitbucket Server
- Changing the port that Bitbucket Server listens on
- Bitbucket サーバーを異なるコンテキスト パスに移動する
- Running Bitbucket Server with a dedicated user
- Bitbucket Server debug logging
- Data recovery and backups
- Lockout recovery process
- Bitbucket Server の拡張
- High availability for Bitbucket Server
- Clustering with Bitbucket Data Center
- Enabling JMX counters for performance monitoring
- Getting started with Bitbucket Server and AWS
- Disabling HTTP(S) access to Git repositories in Bitbucket Server
- スマート ミラーリング
- Git Large File Storage
このページの内容
関連コンテンツ
- Cannot enable or save Automation rule due to the error "Either you or the rule actor for this rule is missing some required permissions"
- Automation rule| After importing Automations rule facing challenges with enabling the rules on destination site
- Unable to change the "owner" or "actor" or "who can edit the rule"of automation rule
- Automation rule is failing with "Actor does not have permission to view one or more issues, or the issue was deleted "
- Automation Rule Actor Missing Permissions in JSM Cloud
- Actor permission error in automation execution log
- Actor permission error in automation execution log
- Automation rule not working after removing the rule actor license
- Automation Rule: Setting Issue Security Level fails
- Permissions required to manage Automation rules
A Bitbucket Server administrator can disable HTTP(S) access to Git repositories in Bitbucket Server. This removes the ability to push to or clone Git repositories in Bitbucket Server over HTTP(S).
Disabling HTTP(S) access
To disable HTTP(S) access:
- Go to the Bitbucket Server administration area and click Server settings (under 'Settings').
- Under 'HTTP(S) access', uncheck HTTP(S) enabled.
- 保存をクリックします。
最終更新日 2015 年 9 月 16 日
関連コンテンツ
- Cannot enable or save Automation rule due to the error "Either you or the rule actor for this rule is missing some required permissions"
- Automation rule| After importing Automations rule facing challenges with enabling the rules on destination site
- Unable to change the "owner" or "actor" or "who can edit the rule"of automation rule
- Automation rule is failing with "Actor does not have permission to view one or more issues, or the issue was deleted "
- Automation Rule Actor Missing Permissions in JSM Cloud
- Actor permission error in automation execution log
- Actor permission error in automation execution log
- Automation rule not working after removing the rule actor license
- Automation Rule: Setting Issue Security Level fails
- Permissions required to manage Automation rules
Powered by Confluence and Scroll Viewport.