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/container-apps/ingress-overview.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,12 +65,12 @@ HTTP ingress adds headers to pass metadata about the client request to your cont
65
65
|`X-Forwarded-For`| The IP address of the client that sent the request. ||
66
66
|`X-Forwarded-Host`| The host name the client used to connect with the Container Apps service. ||
67
67
68
-
### <aname="tcp"></a>TCP (preview)
68
+
### <aname="tcp"></a>TCP
69
69
70
70
Container Apps supports TCP-based protocols other than HTTP or HTTPS. For example, you can use TCP ingress to expose a container app that uses the [Redis protocol](https://redis.io/topics/protocol).
71
71
72
72
> [!NOTE]
73
-
> TCP ingress is in public preview. External TCP ingress setting is only supported in Container Apps environments that use a [custom VNET](vnet-custom.md).
73
+
> External TCP ingress is only supported for Container Apps environments that use a [custom VNET](vnet-custom.md).
0 commit comments