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/application-gateway/redirect-overview.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,29 +12,29 @@ ms.author: mbender
12
12
13
13
# Application Gateway redirect overview
14
14
15
-
You can use application gateway to redirect traffic. It has a generic redirection mechanism which allows for redirecting traffic received at one listener to another listener or to an external site. This simplifies application configuration, optimizes the resource usage, and supports new redirection scenarios including global and path-based redirection.
15
+
You can use application gateway to redirect traffic. It has a generic redirection mechanism, which allows for redirecting traffic received at one listener to another listener or to an external site. This simplifies application configuration, optimizes the resource usage, and supports new redirection scenarios including global and path-based redirection.
16
16
17
-
A common redirection scenario for many web applications is to support automatic HTTP to HTTPS redirection to ensure all communication between application and its users occurs over an encrypted path. In the past, customers have used techniques such as creating a dedicated backend pool whose sole purpose is to redirect requests it receives on HTTP to HTTPS. With redirection support in Application Gateway, you can accomplish this simply by adding a new redirect configuration to a routing rule, and specifying another listener with HTTPS protocol as the target listener.
17
+
A common redirection scenario for many web applications is to support automatic HTTP to HTTPS redirection to ensure all communication between an application and its users occurs over an encrypted path. In the past, customers have used techniques such as creating a dedicated backend pool whose sole purpose is to redirect requests it receives on HTTP to HTTPS. With redirection support in Application Gateway, you can accomplish this simply by adding a new redirect configuration to a routing rule, and specifying another listener with HTTPS protocol as the target listener. For more information on HTTP to HTTPS redirection, see [Create an Application Gateway with HTTP to HTTPS redirection using the Azure portal](redirect-http-to-https-portal.md).
18
18
19
19
## Redirection types
20
20
A redirect type sets the response status code for the clients to understand the purpose of the redirect. The following types of redirection are supported:
21
21
22
-
- 301 (Moved permanently): Indicates that the target resource has been assigned a new permanent URI. Any future references to this resource will use one of the enclosed URIs. Use 301 status code for HTTP to HTTPS redirection.
23
-
- 302 (Found): Indicates that the target resource is temporarily under a different URI. Since the redirection can change on occasion, the client should continue to use the effective request URI for future requests.
24
-
- 303 (See Other): Indicates that the target resource is redirecting the user agent to a different resource, as indicated by a URI in the Location header field.
25
-
- 307 (Temporary redirect): Indicates that the target resource is temporarily under a different URI. The user agent MUST NOT change the request method if it does an automatic redirection to that URI. Since the redirection can change over time, the client ought to continue using the original effective request URI for future requests.
22
+
-**301 (Moved permanently)**: Indicates that the target resource has been assigned a new permanent URI. Any future references to this resource will use one of the enclosed URIs. Use 301 status code for HTTP to HTTPS redirection.
23
+
-**302 (Found)**: Indicates that the target resource is temporarily under a different URI. Since the redirection can change on occasion, the client should continue to use the effective request URI for future requests.
24
+
-**303 (See Other)**: Indicates that the target resource is redirecting the user agent to a different resource, as indicated by a URI in the Location header field.
25
+
-**307 (Temporary redirect)**: Indicates that the target resource is temporarily under a different URI. The user agent MUST NOT change the request method if it does an automatic redirection to that URI. Since the redirection can change over time, the client ought to continue using the original effective request URI for future requests.
26
26
27
27
## Redirection capabilities
28
28
29
-
-**Listener redirection**
29
+
-**Listener redirection**
30
30
31
31
Redirects from one listener to another listener. Listener redirection is commonly used to enable HTTP to HTTPS redirection.
32
32
33
-
When configuring redirects with a multi-site target listener, it is required that all the host names (with or without wildcard characters) are defined as part of the source listener are also part of the destination listener. This ensures that no traffic is dropped due to missing host names on the destination listener while configuring HTTP to HTTPS redirection.
33
+
When configuring redirects with a multi-site target listener, it's required that all the host names (with or without wildcard characters) that are defined as part of the source listener are also part of the destination listener. This ensures that no traffic is dropped due to missing host names on the destination listener while configuring HTTP to HTTPS redirection.
34
34
35
35
-**Path-based redirection**
36
36
37
-
This type of redirection enables redirection only on a specific site area, for example, redirecting HTTP to HTTPS requests for a shopping cart area denoted by /cart/\*.
37
+
This type of redirection enables redirection only on a specific site area, for example, redirecting HTTP to HTTPS requests for a shopping cart area denoted by `/cart/*`.
Copy file name to clipboardExpand all lines: articles/communication-services/quickstarts/email/includes/create-email-resource-dot-net.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,6 +51,7 @@ using Azure.Core;
51
51
usingAzure.Identity;
52
52
usingAzure.ResourceManager;
53
53
usingAzure.ResourceManager.Communication;
54
+
usingAzure.ResourceManager.Communication.Models;
54
55
usingAzure.ResourceManager.Resources;
55
56
...
56
57
// get your azure access token, for more details of how Azure SDK get your access token, please refer to https://learn.microsoft.com/dotnet/azure/sdk/authentication?tabs=command-line
Copy file name to clipboardExpand all lines: articles/event-hubs/monitor-event-hubs-reference.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -237,7 +237,9 @@ Application metrics logs capture the aggregated information on certain metrics r
237
237
238
238
- The following points govern the emission of consumer lag for Kafka consumers.
239
239
- A namespace is idle from Kafka offset commit point of view if there are no offset commits for any Kafka consumer group under the namespace.
240
-
- If namespace is idle for an hour, then emission of lag metrics stops. As long as the namespace is not idle for offset commit, metrics are emitted for all Kafka consumer groups under that namespace.
240
+
- If namespace is idle for an hour, then emission of lag metrics stops.
241
+
242
+
- As long as the namespace is not idle for offset commit, metrics are emitted for all Kafka consumer groups under that namespace.
241
243
- If a namespace is non-idle and the last offset commit for a consumer group predates the hub or topic's retention period, consumer lag will no longer be emitted.
242
244
- For AMQP consumers, consumer lag is emitted only as long as there are active receivers on the consumer group.
0 commit comments