Skip to content

Commit bf72a40

Browse files
committed
Updates
1 parent 9cc7917 commit bf72a40

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/key-vault/general/common-parameters-and-headers.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
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.
44
services: key-vault
55
author: msmbaldwin
66
tags: azure-resource-manager
@@ -15,15 +15,15 @@ ms.author: mbaldwin
1515

1616
# Common parameters and headers
1717

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:
1919

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.
2121
- Replace `{api-version}` with the api-version in the URI.
2222
- Replace `{subscription-id}` with your subscription identifier in the URI
2323
- Replace `{resource-group-name}` with the resource group. For more information, see Using Resource groups to manage your Azure resources.
2424
- Replace `{vault-name}` with your key vault name in the URI.
2525
- 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.
2727

2828
## Common error response
2929
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

Comments
 (0)