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/frontdoor/front-door-faq.yml
+6-1Lines changed: 6 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ metadata:
6
6
ms.author: duau
7
7
ms.service: frontdoor
8
8
ms.topic: faq
9
-
ms.date: 11/08/2023
9
+
ms.date: 06/17/2024
10
10
title: Frequently asked questions for Azure Front Door
11
11
summary: |
12
12
This article answers common questions about Azure Front Door features and functionality. If you don't see the answer to your question, you can contact us through the following channels (in escalating order):
@@ -146,6 +146,11 @@ sections:
146
146
> Custom TLS/SSL certificate updates might take longer, from several minutes up to an hour, to be deployed globally.
147
147
148
148
Updates to routes or origin groups/backend pools are seamless and don't cause any downtime (assuming the new configuration is correct). Certificate updates are also done atomically, so there's no risk of outage.
149
+
150
+
- question: |
151
+
Does Azure Front Door support gRPC?
152
+
answer: |
153
+
No. Currently, Azure Front Door only supports HTTP/1.1 from the edge to the origin. For gRPC to work, HTTP/2 is required.
0 commit comments