Skip to content

Commit ef165b4

Browse files
Merge pull request #231045 from jaesoni/proxy-buffer-cli
Proxy buffer cli
2 parents df3ba0b + 2113119 commit ef165b4

File tree

1 file changed

+16
-3
lines changed

1 file changed

+16
-3
lines changed

articles/application-gateway/proxy-buffers.md

Lines changed: 16 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -36,9 +36,22 @@ You can keep either the Request or Response buffer, enabled or disable, based on
3636
> [!WARNING]
3737
>We strongly recommend that you test and evaluate the performance before rolling this out on the production gateways.
3838
39-
## How to change the buffer setting?
39+
## How to change the buffer settings?
4040

41-
You can change this setting by using GlobalConfiguration in the ARM template as shown below.
41+
You can change this setting by using the globalConfiguration property.
42+
43+
### Azure CLI method
44+
45+
**Response Buffer**
46+
```azurecli-interactive
47+
az network application-gateway update --name <gw-name> --resource-group <rg-name> --set globalConfiguration.enableResponseBuffering=false
48+
```
49+
**Request Buffer**
50+
```azurecli-interactive
51+
az network application-gateway update --name <gw-name> --resource-group <rg-name> --set globalConfiguration.enableRequestBuffering=false
52+
```
53+
54+
### ARM template method
4255

4356
```json
4457
{
@@ -72,5 +85,5 @@ For reference, visit [Azure SDK for .NET](/dotnet/api/microsoft.azure.management
7285

7386
## Limitations
7487
- API version 2020-01-01 or later should be used to configure buffers.
75-
- Currently, these changes are supported only through ARM templates.
88+
- Currently, these changes are not supported through Portal and PowerShell.
7689
- Request and Response Buffers can only be disabled for the WAF v2 SKU if request body checking is disabled. Otherwise, Request and Response Buffers cannot be disabled for the WAF v2 SKU.

0 commit comments

Comments
 (0)