Git リポジトリへの HTTP(S) アクセスの無効化
Bitbucket Data Center と Server の管理
- Users and groups
- 外部ユーザー ディレクトリ
- グローバル権限
- Setting up your mail server
- アトラシアン アプリケーションとの連携
- Connect Bitbucket to an external database
- Migrating Bitbucket Server to another server
- Run Bitbucket in AWS
- Specify the Bitbucket base URL
- Configuring the application navigator
- アプリの管理
- 監査ログの表示と設定
- Update your license key
- Configuration properties
- Bitbucket のコンテキスト パスを変更する
- Data recovery and backups
- Git リポジトリへの HTTP(S) アクセスの無効化
- スマート ミラーリング
- プロジェクトとリポジトリのエクスポートとインポート
- Git Large File Storage
- Git Virtual File System (GVFS)
- Git リポジトリへの SSH アクセスを有効にする
- Use diff transcoding
- Change the port Bitbucket listens on
- Lockout recovery process
- プロキシとセキュアな Bitbucket
- High availability for Bitbucket
- Diagnostics for third-party apps
- Enabling JMX counters for performance monitoring
- Enable debug logging
- Bitbucket Server の拡張
- Add a shortcut link to a repository
- Administer code search
- Adding additional storage for your repository data
- Add a system-wide announcement banner
- アプリケーションを横断したプロジェクト リンクの構成
- レート制限でインスタンスの安定性を改善する
- Atlasssian Data Center アプリケーションで CDN を使用する
- Managing personal access tokens
- Connecting to a 3rd party application using Application Links
- Setting a system-wide default branch name
- 非アクティブなプル リクエストを自動的に却下
- データベース パスワードの暗号化
このページの内容
関連コンテンツ
- Bitbucket Server webhook is not providing git URL is response payload.
- Can't access Bitbucket Server with Git - Issuer certificate is invalid
- Permanently authenticating with Git repositories
- Specify the Bitbucket base URL
- Git command returns "not found" or error code 404
- Bitbucket Server: Git operations fails with error fatal: unable to access.. Encountered end of file
- Unable to push changes to the repository in Bitbucket Server with insufficient permission error over HTTPS URL
- Can't clone or pull due to a git outbound proxy
- How to serve your Bitbucket Server repo without using Bitbucket Server
- Bitbucket does not support Git's legacy HTTP transport protocol when using Git LFS
Administrators can disable HTTP(S) access to Git repositories in Bitbucket Data Center and Server. This removes the ability to push to or clone Git repositories over HTTP(S).
To disable HTTP(S) access:
- Go to
> Server settings.
- Uncheck HTTP(S) enabled.
- [保存] を選択します。
最終更新日 2021 年 5 月 12 日
関連コンテンツ
- Bitbucket Server webhook is not providing git URL is response payload.
- Can't access Bitbucket Server with Git - Issuer certificate is invalid
- Permanently authenticating with Git repositories
- Specify the Bitbucket base URL
- Git command returns "not found" or error code 404
- Bitbucket Server: Git operations fails with error fatal: unable to access.. Encountered end of file
- Unable to push changes to the repository in Bitbucket Server with insufficient permission error over HTTPS URL
- Can't clone or pull due to a git outbound proxy
- How to serve your Bitbucket Server repo without using Bitbucket Server
- Bitbucket does not support Git's legacy HTTP transport protocol when using Git LFS
Powered by Confluence and Scroll Viewport.