Skip to content

Commit ba693a0

Browse files
Update overview-v2.md
1 parent 637165a commit ba693a0

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

articles/application-gateway/overview-v2.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -118,10 +118,9 @@ This section describes features and limitations of the v2 SKU that differ from t
118118
|--|--|
119119
|Mixing Standard_v2 and Standard Application Gateway on the same subnet|Not supported|
120120
|User-Defined Route (UDR) on Application Gateway subnet|For information about supported scenarios, see [Application Gateway configuration overview](configuration-infrastructure.md#supported-user-defined-routes).|
121-
|NSG for Inbound port range| - 65200 to 65535 for Standard_v2 SKU<br>- 65503 to 65534 for Standard SKU.<br>Not required for v2 SKUs in public preview [Learn more](application-gateway-private-deployment.md).<br>For more information, see the [FAQ](application-gateway-faq.yml#are-network-security-groups-supported-on-the-application-gateway-subnet).|
121+
|NSG for Inbound port range| - 65200 to 65535 for Standard_v2 SKU<br>- 65503 to 65534 for Standard SKU.<br>Not required for v2 SKUs in private deployment [Learn more](application-gateway-private-deployment.md).<br>For more information, see the [FAQ](application-gateway-faq.yml#are-network-security-groups-supported-on-the-application-gateway-subnet).|
122122
|Performance logs in Azure diagnostics|Not supported.<br>Azure metrics should be used.|
123123
|FIPS mode|Currently not supported.|
124-
|Private frontend configuration only mode|Currently in public preview [Learn more](application-gateway-private-deployment.md).|
125124
|Path based rule encoding |Not supported.<br> V2 decodes paths before routing. For example, V2 treats `/abc%2Fdef` the same as `/abc/def`. |
126125
|Chunked file transfer |In the Standard_V2 configuration, turn off request buffering to support chunked file transfer. <br> In WAF_V2, turning off request buffering isn't possible because it has to look at the entire request to detect and block any threats. Therefore, the suggested alternative is to create a path rule for the affected URL and attach a disabled WAF policy to that path rule.|
127126
|Cookie Affinity |Current V2 doesn't support appending the domain in session affinity Set-Cookie, which means that the cookie can't be used by client for the subdomains.|

0 commit comments

Comments
 (0)