Skip to content

Commit 2fd3dd3

Browse files
Update networking.md
1 parent 45fba22 commit 2fd3dd3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/container-apps/networking.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -337,9 +337,9 @@ The following example shows an environment with peer-to-peer encryption enabled.
337337

338338
<sup>2</sup> Traffic to and from the ingress proxy within the environment is TLS encrypted with a private certificate and decrypted by the receiver.
339339

340-
<sup>3</sup> Calls made from app A to app B's FQDN are first sent to the edge ingress proxy, and are TLS encrypted.
340+
<sup>3</sup> Calls made from app A to app B's FQDN are first sent to the edge ingress proxy, and are TLS encrypted.
341341

342-
<sup>4</sup> Calls made from app A to app B using app B's app name are sent directly to app B and are TLS encrypted.
342+
<sup>4</sup> Calls made from app A to app B using app B's app name are sent directly to app B and are TLS encrypted. Calls between apps and [Java components](java-overview#java-components-support) are treated in the same way as app to app communication and TLS encrypted.
343343

344344
Applications within a Container Apps environment are automatically authenticated. However, the Container Apps runtime doesn't support authorization for access control between applications using the built-in peer-to-peer encryption.
345345

0 commit comments

Comments
 (0)