You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/key-vault/general/common-parameters-and-headers.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Common parameters and headers
3
-
description: The parameters and headers common to all operations that you might do related to Key Vault resources.
3
+
description: The parameters and headers common to all operations that you might perform on Key Vault resources.
4
4
services: key-vault
5
5
author: msmbaldwin
6
6
tags: azure-resource-manager
@@ -15,15 +15,15 @@ ms.author: mbaldwin
15
15
16
16
# Common parameters and headers
17
17
18
-
The following information is common to all operations that you might do related to Key Vault resources:
18
+
The following information is common to all operations that you might perform on Key Vault resources:
19
19
20
-
- The HTTP `Host` header must always be present and must specify the vault hostname. Example: `Host: contoso.vault.azure.net`. Note that most client technologies populate the `Host` header from the URI. For instance, `GET https://contoso.vault.azure.net/secrets/mysecret{...}` will set the `Host` as `contoso.vault.azure.net`. This means that if you access Key Vault using raw IP address like `GET https://10.0.0.23/secrets/mysecret{...}`, the automatic value of `Host` header will be wrong and you will have to manually insure that the `Host` header contains the vault hostname.
20
+
- The HTTP `Host` header must always be present and must specify the vault hostname. Example: `Host: contoso.vault.azure.net`. Note that most client technologies populate the `Host` header from the URI. For instance, `GET https://contoso.vault.azure.net/secrets/mysecret{...}` will set the `Host` as `contoso.vault.azure.net`. If you access Key Vault using raw IP address like `GET https://10.0.0.23/secrets/mysecret{...}`, the automatic value of `Host` header will be wrong, and you'll have to manually ensure that the `Host` header contains the vault hostname.
21
21
- Replace `{api-version}` with the api-version in the URI.
22
22
- Replace `{subscription-id}` with your subscription identifier in the URI
23
23
- Replace `{resource-group-name}` with the resource group. For more information, see Using Resource groups to manage your Azure resources.
24
24
- Replace `{vault-name}` with your key vault name in the URI.
25
25
- Set the Content-Type header to application/json.
26
-
- Set the Authorization header to a JSON Web Token that you obtain from Azure Active Directory (AAD). For more information, see [Authenticating Azure Resource Manager](authentication-requests-and-responses.md) requests.
26
+
- Set the Authorization header to a JSON Web Token that you obtain from Azure Active Directory (Azure AD). For more information, see [Authenticating Azure Resource Manager](authentication-requests-and-responses.md) requests.
27
27
28
28
## Common error response
29
29
The service will use HTTP status codes to indicate success or failure. In addition, failures contain a response in the following format:
0 commit comments