To explain this process further, let's look at an example configuration of Front Door routes (left-hand side only): Routing rule If no exact frontend hosts match, reject the request and send a 400 Bad Request error.Look for any routing with an exact match on the host.When matching Frontend hosts, we use the logic defined below: We first match based on HTTP protocol, then Frontend host, then the Path. The basic concept is that we always match to the most-specific match first looking only at the "left-hand side". This section will focus on how we match to a given Front Door routing rule. If a cached response isn't available, then the request is forwarded to the appropriate backend. The decision of how to process the request, depends on whether caching is enabled or not for the Route. ![]() These properties are expanded out internally so that every combination of Protocol/Host/Path is a potential match set.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |