Skip to content

Commit 36a3b3f

Browse files
authored
Merge pull request #114030 from erikadoyle/sfrevproxy
Add note for configuring https on Service Fabric reverse proxy
2 parents 6cc0eb2 + 6d28eae commit 36a3b3f

File tree

1 file changed

+4
-7
lines changed

1 file changed

+4
-7
lines changed

articles/service-fabric/service-fabric-reverseproxy-configure-secure-communication.md

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,15 @@
11
---
22
title: Azure Service Fabric reverse proxy secure communication
33
description: Configure reverse proxy to enable secure end-to-end communication in an Azure Service Fabric application.
4-
author: kavyako
5-
64
ms.topic: conceptual
75
ms.date: 08/10/2017
8-
ms.author: kavyako
96
---
107
# Connect to a secure service with the reverse proxy
118

129
This article explains how to establish secure connection between the reverse proxy and services, thus enabling an end to end secure channel. To learn more about reverse proxy, see [Reverse proxy in Azure Service Fabric](service-fabric-reverseproxy.md)
1310

14-
Connecting to secure services is supported only when reverse proxy is configured to listen on HTTPS. This article assumes this is the case.
15-
Refer to [Setup reverse proxy in Azure Service Fabric](service-fabric-reverseproxy-setup.md) to configure the reverse proxy in Service Fabric.
11+
> [!IMPORTANT]
12+
> Connecting to secure services is supported only when reverse proxy is configured to listen on HTTPS. This article assumes this is the case. Refer to [Setup reverse proxy in Azure Service Fabric](service-fabric-reverseproxy-setup.md) to configure the reverse proxy in Service Fabric.
1613
1714
## Secure connection establishment between the reverse proxy and services
1815

@@ -177,10 +174,10 @@ This is the default behavior.
177174

178175
2. When **ForwardClientCertificate** is set to **true**, reverse proxy requests the client's certificate during its TLS handshake with the client.
179176
It will then forward the client certificate data in a custom HTTP header named **X-Client-Certificate**. The header value is the base64 encoded PEM format string of the client's certificate. The service can succeed/fail the request with appropriate status code after inspecting the certificate data.
180-
If the client does not present a certificate, reverse proxy forwards an empty header and let the service handle the case.
177+
If the client does not present a certificate, reverse proxy forwards an empty header and lets the service handle the case.
181178

182179
> [!NOTE]
183-
> Reverse proxy is a mere forwarder. It will not perform any validation of the client's certificate.
180+
> Reverse proxy acts only as a forwarding service. It will not perform any validation of the client's certificate.
184181
185182

186183
## Next steps

0 commit comments

Comments
 (0)