tencent cloud

Cloud Object Storage

동향 및 공지
릴리스 노트
제품 공지
제품 소개
제품 개요
기능 개요
적용 시나리오
제품 장점
기본 개념
리전 및 액세스 도메인
규격 및 제한
제품 요금
과금 개요
과금 방식
과금 항목
프리 티어
과금 예시
청구서 보기 및 다운로드
연체 안내
FAQ
빠른 시작
콘솔 시작하기
COSBrowser 시작하기
사용자 가이드
요청 생성
버킷
객체
데이터 관리
일괄 프로세스
글로벌 가속
모니터링 및 알람
운영 센터
데이터 처리
스마트 툴 박스 사용 가이드
데이터 워크플로
애플리케이션 통합
툴 가이드
툴 개요
환경 설치 및 설정
COSBrowser 툴
COSCLI 툴
COSCMD 툴
COS Migration 툴
FTP Server 툴
Hadoop 툴
COSDistCp 툴
HDFS TO COS 툴
온라인 도구 (Onrain Dogu)
자가 진단 도구
실습 튜토리얼
개요
액세스 제어 및 권한 관리
성능 최적화
AWS S3 SDK를 사용하여 COS에 액세스하기
데이터 재해 복구 백업
도메인 관리 사례
이미지 처리 사례
COS 오디오/비디오 플레이어 사례
데이터 다이렉트 업로드
데이터 보안
데이터 검증
빅 데이터 사례
COS 비용 최적화 솔루션
3rd party 애플리케이션에서 COS 사용
마이그레이션 가이드
로컬 데이터 COS로 마이그레이션
타사 클라우드 스토리지 데이터를 COS로 마이그레이션
URL이 소스 주소인 데이터를 COS로 마이그레이션
COS 간 데이터 마이그레이션
Hadoop 파일 시스템과 COS 간 데이터 마이그레이션
데이터 레이크 스토리지
클라우드 네이티브 데이터 레이크
메타데이터 가속
데이터 레이크 가속기 GooseFS
데이터 처리
데이터 처리 개요
이미지 처리
미디어 처리
콘텐츠 조정
파일 처리
문서 미리보기
장애 처리
RequestId 가져오기
공용 네트워크로 COS에 파일 업로드 시 속도가 느린 문제
COS 액세스 시 403 에러 코드 반환
리소스 액세스 오류
POST Object 자주 발생하는 오류
보안 및 컴플라이언스
데이터 재해 복구
데이터 보안
액세스 관리
자주 묻는 질문
인기 질문
일반 문제
과금
도메인 규정 준수 문제
버킷 설정 문제
도메인 및 CDN 문제
파일 작업 문제
로그 모니터링 문제
권한 관리
데이터 처리 문제
데이터 보안 문제
사전 서명 URL 관련 문제
SDK FAQ
툴 관련 문제
API 관련 문제
Agreements
Service Level Agreement
개인 정보 보호 정책
데이터 처리 및 보안 계약
연락처
용어집
문서Cloud Object Storage

PUT Bucket website

포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-02-27 15:28:28

Overview

This API is used to configure a static website for a bucket by importing configuration files in XML format. The file size is limited to 64 KB.
Note:
If a bucket already has a static website configuration, calling this API will overwrite the existing static website configuration information.


Authorization Description

In the authorization policy, action is set to cos:PutBucketWebsite. View all action.

Request

Sample request

PUT /?website HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: GMT Date
Content-Type: application/xml
Content-Length: Content Length
Content-MD5: MD5
Authorization: Auth String

[Request Body]
Note:
In Host: <BucketName-APPID>.cos.<Region>.myqcloud.com, <BucketName-APPID> is the bucket name followed by the APPID, such as examplebucket-1250000000 (see Bucket Overview > Basic Information and Bucket Overview > Bucket Naming Conventions), and <Region> is a COS region (see Regions and Access Endpoints).
Authorization: Auth String (See Request Signature for details.)

Request parameters

This API has no request parameter.

Request headers

This API only uses Common Request Headers.

Request body

This request body submits the application/xml data that includes all information about the static website configuration of the bucket.
<WebsiteConfiguration>
    <IndexDocument>
        <Suffix>String</Suffix>
    </IndexDocument>
    <RedirectAllRequestsTo>
        <Protocol>String</Protocol>
    </RedirectAllRequestsTo>
    <AutoAddressing>
        <Status>Enabled|Disabled</Status>
    </AutoAddressing>
    <ErrorDocument>
        <Key>String</Key>
        <Charity404>Enabled|Disabled</Charity404>
        <OriginalHttpStatus>Enabled|Disabled</OriginalHttpStatus>
    </ErrorDocument>
    <RoutingRules>
        <RoutingRule>
            <Condition>
                <HttpErrorCodeReturnedEquals>Integer</HttpErrorCodeReturnedEquals>
            </Condition>
            <Redirect>
                <Protocol>String</Protocol>
                <ReplaceKeyWith>String</ReplaceKeyWith>
                <URLRedirect>Enabled|Disabled</URLRedirect>
            </Redirect>
        </RoutingRule>
        <RoutingRule>
            <Condition>
                <KeyPrefixEquals>String</KeyPrefixEquals>
            </Condition>
            <Redirect>
                <Protocol>String</Protocol>
                <ReplaceKeyPrefixWith>String</ReplaceKeyPrefixWith>
                <URLRedirect>Enabled|Disabled</URLRedirect>
            </Redirect>
        </RoutingRule>
    </RoutingRules>
</WebsiteConfiguration>
The nodes are described as follows:
Node Name (Keyword)
Parent Node
Description
Type
Required
WebsiteConfiguration
None
Contains all the request information about PUT Bucket website
Container
Yes
Content of WebsiteConfiguration:
Node Name (Keyword)
Parent Node
Description
Type
Required
IndexDocument
WebsiteConfiguration
Index document configuration
Container
Yes
RedirectAllRequestsTo
WebsiteConfiguration
Configures redirection for all requests
Container
No
AutoAddressing
WebsiteConfiguration
Whether to ignore all file extensions
Container
No
ErrorDocument
WebsiteConfiguration
Error document configuration
Container
No
RoutingRules
WebsiteConfiguration
Routing rule configuration. A RoutingRules container can contain up to 100 RoutingRule elements.
Container
No
Content of IndexDocument:
Node Name (Keyword)
Parent Node
Description
Type
Required
Suffix
WebsiteConfiguration.IndexDocument
Specifies the object key suffix for index documents. For example, if it is specified as index.html, the request automatically returns index.html when you access the root directory of the bucket, or article/index.html when you access the directory article/.
String
Yes
Content of RedirectAllRequestsTo:
Node Name (Keyword)
Parent Node
Description
Type
Required
Protocol
WebsiteConfiguration.RedirectAllRequestsTo
Specifies the target protocol to redirect all requests. Only HTTPS is supported.
String
No
Content of AutoAddressing:
Node Name (Keyword)
Parent Node
Description
Type
Required
Status
WebsiteConfiguration.AutoAddressing
Whether to ignore the HTML file extension. Valid values: Enabled, Disabled (default)
String
No
Content of ErrorDocument:
Node Name (Keyword)
Parent Node
Description
Type
Required
Key
WebsiteConfiguration.ErrorDocument
Specifies the object key to return for the error document if an error occurs and does not match the error code in the routing rule
String
No
OriginalHttpStatus
WebsiteConfiguration.ErrorDocument
Configures whether to return the corresponding HTTPS status code if the error documents are hit. Valid values: Enabled (default), Disabled
String
No
Charity404
WebsiteConfiguration.ErrorDocument
Configures whether to display the 404 public welfare page when the error code is 404. Valid values: Enabled or Disabled. Default: Disabled.
String
No
Content of RoutingRules:
Node Name (Keyword)
Parent Node
Description
Type
Required
RoutingRule
WebsiteConfiguration.RoutingRules
A single routing rule
Container
Yes
Content of RoutingRules.RoutingRule:
Node Name (Keyword)
Parent Node
Description
Type
Required
Condition
WebsiteConfiguration.RoutingRules.RoutingRule
Condition for the routing rule
Container
Yes
Redirect
WebsiteConfiguration.RoutingRules.RoutingRule
Configuration of the redirection target
Container
Yes
Content of RoutingRules.RoutingRule.Condition:
Node Name (Keyword)
Parent Node
Description
Type
Required
HttpErrorCodeReturnedEquals
WebsiteConfiguration.RoutingRules.RoutingRule.Condition
Specifies the error code as the match condition for the routing rule. Valid values: only 4xx return codes, such as 403 or 404.
Integer
Either this parameter or KeyPrefixEquals must be specified.
KeyPrefixEquals
WebsiteConfiguration.RoutingRules.RoutingRule.Condition
Specifies the object key prefix as the match condition for the routing rule
String
Either this parameter or HttpErrorCodeReturnedEquals must be specified.
Content of RoutingRules.RoutingRule.Redirect:
Node Name (Keyword)
Parent Node
Description
Type
Required
Protocol
WebsiteConfiguration.RoutingRules.RoutingRule.Redirect
Specifies the target protocol for the routing rule. Only HTTPS is supported.
String
No
ReplaceKeyWith
WebsiteConfiguration.RoutingRules.RoutingRule.Redirect
Specifies the target object key to replace the original object key in the request.
String
Either this parameter or ReplaceKeyPrefixWith must be specified.
ReplaceKeyPrefixWith
WebsiteConfiguration.RoutingRules.RoutingRule.Redirect
Specifies the object key prefix to replace the original prefix in the request. You can set this parameter only if the condition is KeyPrefixEquals.
String
Either this parameter or ReplaceKeyWith must be specified.
URLRedirect
WebsiteConfiguration.RoutingRules.RoutingRule.Redirect
Whether the URL in the redirect rule changes according to the replacement content. Valid values: Enabled, Disabled. The default value is Enabled.
String
No

Response

Response headers

This API only returns Common Response Headers.

Response body

The response body of this API is empty.

Error codes

This API returns common error responses and error codes. For more information, please see Error Codes.

Samples

Request

PUT /?website HTTP/1.1
Host: examplebucket-1250000000.cos.ap-beijing.myqcloud.com
Date: Wed, 20 May 2020 09:33:38 GMT
Content-Type: application/xml
Content-Length: 1209
Content-MD5: VHzj4Uwb++HLyCJp7jUzWg==
Authorization: q-sign-algorithm=sha1&q-ak=AKID8A0fBVtYFrNm02oY1g1JQQF0c3JO****&q-sign-time=1589967218;1589974418&q-key-time=1589967218;1589974418&q-header-list=content-length;content-md5;content-type;date;host&q-url-param-list=website&q-signature=4666493555640e834a879c78afaa4fd9b16a****
Connection: close

<WebsiteConfiguration>
    <IndexDocument>
        <Suffix>index.html</Suffix>
    </IndexDocument>
    <RedirectAllRequestsTo>
        <Protocol>https</Protocol>
    </RedirectAllRequestsTo>
    <ErrorDocument>
        <Key>pages/error.html</Key>
    </ErrorDocument>
    <RoutingRules>
        <RoutingRule>
            <Condition>
                <HttpErrorCodeReturnedEquals>403</HttpErrorCodeReturnedEquals>
            </Condition>
            <Redirect>
                <Protocol>https</Protocol>
                <ReplaceKeyWith>pages/403.html</ReplaceKeyWith>
            </Redirect>
        </RoutingRule>
        <RoutingRule>
            <Condition>
                <HttpErrorCodeReturnedEquals>404</HttpErrorCodeReturnedEquals>
            </Condition>
            <Redirect>
                <ReplaceKeyWith>pages/404.html</ReplaceKeyWith>
            </Redirect>
        </RoutingRule>
        <RoutingRule>
            <Condition>
                <KeyPrefixEquals>assets/</KeyPrefixEquals>
            </Condition>
            <Redirect>
                <ReplaceKeyWith>index.html</ReplaceKeyWith>
            </Redirect>
        </RoutingRule>
        <RoutingRule>
            <Condition>
                <KeyPrefixEquals>article/</KeyPrefixEquals>
            </Condition>
            <Redirect>
                <Protocol>https</Protocol>
                <ReplaceKeyPrefixWith>archived/</ReplaceKeyPrefixWith>
            </Redirect>
        </RoutingRule>
    </RoutingRules>
</WebsiteConfiguration>

Response

HTTP/1.1 200 OK
Content-Length: 0
Connection: close
Date: Wed, 20 May 2020 09:33:38 GMT
Server: tencent-cos
x-cos-request-id: NWVjNGY5NzJfOThjMjJhMDlfMjg5Ml8yYzNi****

FAQs

Error Documents, 404 Default Pages, and Redirect Rules Take Effect in the Following Order of Precedence

If the user has configured the error document, enabled the 404 public welfare page, and set redirect rules simultaneously, the priority order when all three are triggered is: redirect rules > 404 public welfare page > error document.
다음 주제: 릴리스 노트

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백