經約定之網站變更 v2

Agreed-Upon Change to Website v2

Confirming the Applicant’s control over the ADN by verifying that the Request Token or Random Value is contained in the contents of a file.

透過驗證特定檔案內容中所包含的請求符記（Request Token）或隨機值（Random Value），以確認申請者（Applicant）對經授權網域名稱（Authorization Domain Name，ADN）的控管權。

1. The entire Request Token or Random Value MUST NOT appear in the request used to retrieve the file, and
2. the CA MUST receive a successful HTTP response from the request (meaning a 2xx HTTP status code must be received).

1. 完整的請求符記或隨機值不得（MUST NOT）出現於用來獲取該檔案的請求路徑中，且
2. CA 應（MUST）從該請求收到成功的 HTTP 回應（意即必須收到 2xx HTTP 狀態碼）。

The file containing the Request Token or Random Value:

1. MUST be located on the ADN, and
2. MUST be located under the “/.well-known/pki-validation” directory, and
3. MUST be retrieved via either the “http” or “https” scheme, and
4. MUST be accessed over an Authorized Port.

內容包含請求符記或隨機值的特定檔案：

1. 應（MUST）位於該經授權網域名稱（ADN）之網址，且
2. 應（MUST）位於 “/.well-known/pki-validation” 目錄下，且
3. 應（MUST）透過 “http” 或 “https” 協定獲取，且
4. 應（MUST）透過授權連接埠（Authorized Port）存取。

If the CA follows redirects, the following apply:

1. Redirects MUST be initiated at the HTTP protocol layer. Redirects MUST be the result of a 301, 302, or 307 HTTP status code response, as defined in RFC 7231, Section 6.4, or a 308 HTTP status code response, as defined in RFC 7538, Section 3. Redirects MUST be to the final value of the Location HTTP response header, as defined in RFC 7231, Section 7.1.2.
2. Redirects MUST be to resource URLs with either the “http” or “https” scheme.
3. Redirects MUST be to resource URLs accessed via Authorized Ports.

若 CA 接受並遵從重新導向（redirects），則必須符合以下規定：

1. 重新導向應（MUST）於 HTTP 協定層發起。重新導向應（MUST）由狀態碼為 RFC 7231 第 6.4 節 所定義之 301、302 或 307，或 RFC 7538 第 3 節 所定義之 308 的 HTTP 回應所觸發。重新導向的目標應（MUST）為 RFC 7231 第 7.1.2 節 所定義之 HTTP 回應標頭 Location 的最終值。
2. 重新導向應（MUST）導向具有 “http” 或 “https” 協定的資源 URL 網址。
3. 重新導向應（MUST）導向經由授權連接埠（Authorized Ports）存取的資源 URL 網址。

If a Random Value is used, then:

1. The CA MUST provide a Random Value unique to the certificate request.
2. The Random Value MUST remain valid for use in a confirming response for no more than 30 days from its creation. The CPS MAY specify a shorter validity period for Random Values, in which case the CA MUST follow its CPS.

若使用隨機值（Random Value），則：

1. CA 應（MUST）針對該憑證申請提供唯一的隨機值。
2. 隨機值自建立之日起，用於確認回覆的有效期限應（MUST）不超過 30 日。憑證實務作業基準（Certification Practice Statement，CPS）得（MAY）規定更短的隨機值有效期限，在此情況下，CA 應（MUST）遵從其憑證實務作業基準（CPS）。

Except for Onion Domain Names, CAs performing validations using this method MUST implement Multi-Perspective Issuance Corroboration as specified in Section 3.2.2.9. To count as corroborating, a Network Perspective MUST observe the same challenge information (i.e. Random Value or Request Token) as the Primary Network Perspective.

除 Onion 網域名稱（Onion Domain Names）外，使用此方法進行驗證的 CA 應（MUST）實施第 3.2.2.9 節所規範之多視角簽發佐證（Multi-Perspective Issuance Corroboration）。若要算作有效佐證，其他網路視角（Network Perspective）應（MUST）觀察到與主要網路視角（Primary Network Perspective）相同的挑戰資訊（即隨機值或請求符記）。