Meta tags:
description=Overview of traffic management capabilities for the classic Application Load Balancer.;

Headings (most frequently used words):

and, based, path, rules, traffic, management, routing, host, with, configuring, parameter, rule, route, overview, for, classic, application, load, balancer, stay, organized, collections, save, categorize, content, on, your, preferences, components, use, case, examples, requests, to, backends, rewrites, redirects, header, simple, advanced, products, pricing, support, resources, engage, supported, response, codes, example, testing, query, matchers, match,

Text of the page (most frequently used words):
the (203), load (93), and (90), backend (67), balancer (66), url (64), for (47), set (46), path (42), #overview (41), with (40), cloud (38), request (37), host (37), service (37), traffic (36), rules (36), backends (35), http (30), based (29), you (29), management (28), global (27), rule (27), match (26), can (25), map (24), following (24), neg (24), redirect (23), routerules (23), example (23), route (23), application (23), are (21), use (21), using (21), instance (20), external (19), group (19), https (17), balancing (17), other (16), this (16), routing (16), when (16), google (15), see (15), more (14), matchrules (14), that (14), zonal (14), pathmatchers (13), requests (13), hybrid (13), information (12), query (12), action (11), configure (11), custom (11), services (11), managed (11), header (10), name (10), pathrules (10), simple (10), buckets (10), classic (10), regional (10), architecture (9), parameter (9), rewrite (9), api (9), documentation (9), headers (9), one (9), actions (9), priority (9), matches (9), maps (9), redirects (9), capabilities (9), examples (8), your (8), parameters (8), video (8), com (8), from (8), different (8), pathmatcher (8), advanced (8), web (8), run (8), storage (8), internet (8), internal (8), balancers (8), ssl (8), resources (7), all (7), thumb (7), policies (7), which (7), default (7), engine (7), serverless (7), proxy (7), negs (7), mtls (7), add (7), code (6), configuration (6), matching (6), specify (6), only (6), where (6), evaluated (6), multiple (6), any (6), matcher (6), order (6), create (6), defined (6), testing (6), network (6), sends (6), urls (6), target (6), premises (6), cross (6), shared (6), vpc (6), support (5), page (5), list (5), these (5), supported (5), get (5), matched (5), description (5), effect (5), routerule (5), first (5), compute (5), response (5), rewrites (5), forwarding (5), troubleshooting (5), metrics (5), tcp (5), português (4), español (4), down (4), content (4), setting (4), provides (4), within (4), such (4), allow (4), paths (4), portion (4), domain (4), take (4), field (4), before (4), same (4), components (4), options (4), case (4), defaultservice (4), hostrules (4), hosts (4), choose (4), queryparametermatches (4), abtest (4), user (4), tools (4), ipv6 (4), certificates (4), view (4), logs (4), monitor (4), troubleshoot (4), terraform (4), region (4), site (3), samples (3), need (3), send (3), semantics (3), console (3), configuring (3), images (3), attributes (3), specified (3), routeaction (3), criteria (3), met (3), cannot (3), used (3), resource (3), have (3), described (3), table (3), corresponding (3), made (3), incoming (3), mutually (3), exclusive (3), after (3), each (3), provide (3), backendservices (3), next (3), found (3), figure (3), diagram (3), mode (3), app (3), functions (3), backendserviceforprocessingoptionb (3), backendserviceforprocessingoptiona (3), test (3), mydomain (3), pages (3), feature (3), codes (3), img1 (3), security (3), protocol (3), latency (3), both (3), bucket (3), high (3), takes (3), features (3), guides (3), networking (3), health (3), connectivity (3), tls (3), frontend (3), explore (3), tutorials (3), connected (3), networks (3), directory (3), registration (3), distribution (3), udp (3), migrate (3), 한국어 (2), 日本語 (2), עברית (2), brasil (2), italiano (2), indonesia (2), français (2), américa (2), latina (2), deutsch (2), english (2), sign (2), third (2), terms (2), youtube (2), started (2), notes (2), pricing (2), products (2), understand (2), last (2), updated (2), 2026 (2), utc (2), licensed (2), under (2), license (2), feedback (2), full (2), fields (2), help (2), yaml (2), gcloud (2), well (2), curl (2), address (2), net (2), some (2), urlredirect (2), allows (2), against (2), has (2), routeactions (2), optional (2), number (2), given (2), applied (2), stops (2), executes (2), them (2), evaluates (2), enables (2), contain (2), variety (2), configured (2), specifies (2), reaches (2), single (2), routed (2), instead (2), additional (2), compared (2), longest (2), pathmap (2), ext (2), goes (2), specific (2), does (2), flow (2), shows (2), two (2), modes (2), between (2), selects (2), endpoint (2), exactmatch (2), requirements (2), value (2), called (2), make (2), string (2), proxies (2), method (2), retained (2), 302 (2), back (2), redirecting (2), japan (2), server (2), created (2), names (2), client (2), www (2), someimage (2), jpg (2), transforming (2), friendly (2), easier (2), users (2), into (2), search (2), level (2), perform (2), max (2), sdk (2), languages (2), frameworks (2), infrastructure (2), costs (2), usage (2), access (2), observability (2), monitoring (2), migration (2), industry (2), solutions (2), distributed (2), multicloud (2), databases (2), data (2), analytics (2), pipelines (2), hosting (2), development (2), logging (2), pools (2), tags (2), checks (2), optimizations (2), authorization (2), workload (2), identity (2), failover (2), protocols (2), concepts (2), pool (2), convert (2), capacity (2), over (2), error (2), constraints (2), product (2), reference (2), technology (2), areas (2), close (2), subscribe, newsletter, our, decade, climate, join, manage, cookies, privacy, about, tech, twitter, events, blog, engage, training, certification, center, getting, github, system, status, release, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, otherwise, noted, details, java, registered, trademark, oracle, its, affiliates, developers, apache, creative, commons, attribution, including, regarding, relationships, restrictions, cardinality, writing, files, chosen, environment, configurations, complete, cookie, variables, note, regular, expression, values, isn, follow, whether, entire, leading, needs, comes, shown, command, balanced, respond, conjunction, subset, must, matchrule, partial, directed, 024, characters, through, 147, 483, 647, assigned, determine, evaluation, highest, lowest, numbers, gaps, they, don, contiguous, 2147483647, component, several, applies, looking, looks, performs, evaluating, remaining, ignored, logic, detailed, various, types, prefix, modifiers, insensitivity, presence, makes, decision, generally, intended, type, previously, additionally, sending, matchers, consists, sections, explain, earlier, but, enable, patterns, also, modify, executed, rather, than, describe, typical, might, look, something, like, basis, most, not, initially, entries, associated, logical, work, chooses, outside, containers, means, kubernetes, gke, node, vms, mig, virtual, machine, instances, unmanaged, determined, phased, approach, settings, summarized, suppose, want, sure, handled, follows, how, experiment, input, selected, select, delivering, experiences, categories, devices, originate, assigning, customers, sets, running, simplify, without, deploying, tiers, nginx, decisions, 303, see_other, 307, temporary_redirect, 308, permanent_redirect, 301, moved_permanently_default, listed, browser, location, improves, profile, layer, itself, opposed, implementing, rejecting, sent, meet, compliance, hipaa, encrypted, further, specifically, reduce, edge, result, lower, endpoints, avoid, toil, inefficiencies, workarounds, necessary, belonging, owner, refer, prevent, broken, links, moved, become, outdated, shortening, facing, substantially, shorter, issues, long, issue, formed, modifying, either, stripping, out, retaining, includes, capability, another, uses, myorigin, august_snapshot, static, replaces, directing, reads, separates, translate, human, remember, engines, find, implementation, present, addresses, many, cases, section, few, alternative, appear, unlike, doesn, matter, examined, none, urlmap, pathrule, three, levels, primary, background, topics, fine, tune, behavior, rates, connections, timeouts, intelligently, steering, supports, functionality, gives, available, expanded, save, categorize, preferences, stay, organized, collections, home, clean, setup, check, audit, operate, maintain, size, quota, units, subnets, groups, dns, firewall, connection, draining, customize, post, quantum, authenticated, private, provided, mutual, encryption, self, secure, switch, deploy, hub, spoke, hop, common, party, appliances, hops, affinity, weighted, passthrough, optimize, deliver, published, faster, performance, improved, protection, multi, best, practices, fail, availability, roll, responses, project, organization, policy, iam, conditions, roles, permissions, comparison, model, discover, start, free, skip, main,

Text of the page (random words):
e load balancer s url map for background information see the following topics url map overview using url maps backend services overview traffic management components at a high level external application load balancers provide traffic management by using global url maps the load balancer provides the following mutually exclusive primary actions route requests to a backend service perform a redirect when you set up a load balancer you can configure a url rewrite action before the load balancer sends requests to the backend service or backend bucket rewrites or redirects can be applied at three levels in the url map at the pathrule where the action takes effect when a path is matched at the pathmatcher where the action takes effect when no paths are matched for this pathmatcher at the urlmap where the action takes effect when none of the hosts specified in any of the host rules are matched using routerules in a pathmatcher is an alternative to using pathrules pathrules and routerules cannot both appear in the same pathmatcher unlike pathrules where order doesn t matter routerules are examined in order a routerule can test the url path http headers and url query parameters use case examples traffic management addresses many use cases this section provides a few high level examples rewrites url rewrites allow you to present external users with urls that are different from the urls that your services use a url rewrite separates a url from a resource you can translate from human friendly urls which are easier for users to remember and use transforming them into search engine friendly urls which are easier for search engines to find or into internal implementation specific urls the url rewrite feature does the following reads the incoming url in the request replaces the host the path or both the host and the path transforming the url before directing traffic to the backend service or backend bucket in the following diagram a user in japan sends a request for the url www mydomain com static images someimage jpg when the request reaches the external application load balancer the load balancer uses information in the url map to rewrite the url to www myorigin com august_snapshot images someimage jpg optional in this example the url map sends the request to an external backend figure 1 url rewrite with the classic application load balancer for a configuration example see rewrites redirects with url redirects you can redirect client requests from one url to another url this includes the capability to redirect all http requests to https requests redirect to a different url formed by modifying the host path or both the host and path portion of the url and either stripping out or retaining any query parameters choose which redirect response codes to issue use url redirects for the following capabilities provide url shortening client facing urls can be made substantially shorter this service issues a redirect to the web page with the long url prevent broken links when web pages are moved or become outdated allow multiple domain names belonging to the same owner to refer to a single web site avoid the toil and inefficiencies of configuring workarounds at the backend server to support the necessary redirect reduce latency redirects created at the edge can result in lower latency compared to redirects created at the backend endpoints http to https redirects further specifically help you to meet compliance requirements such as hipaa for encrypted traffic redirect requests using https instead of rejecting requests sent with the http protocol improves the security profile of your application by redirecting the traffic at the layer 7 load balancer itself as opposed to implementing the redirect at the backend server in the following diagram a user in japan sends a get http example com img1 request based on the redirect defined in the url map the load balancer sends back an http 1 1 302 found location https example com img1 redirect redirecting the http request to an https request the user s browser sends a get https example com img1 request figure 2 url redirect with the classic application load balancer for a configuration example see redirects supported response codes the supported redirect response codes are listed in the table response code number notes moved_permanently_default 301 found 302 permanent_redirect 308 in this case the request method is retained temporary_redirect 307 in this case the request method is retained see_other 303 header based and parameter based routing header based and parameter based routing allow a load balancer to make routing decisions that are based on http headers and url query parameters with this feature you can simplify your cloud architecture without deploying additional tiers of proxies nginx for example to do routing you can use the external application load balancer to do the following a b testing assigning customers to different sets of services running on backends delivering different pages and experiences based on different categories of devices from which the requests originate after a pathmatcher is selected based on the host string the routerules in the pathmatcher select a url path for more information see the url maps overview example configuring a b testing with query parameter based routing the following example shows how to do a b testing by matching on the query string to specify the experiment and input suppose that you want to make sure that requests are handled as follows all requests with the query parameter value a go to the backend service called backendserviceforprocessingoptiona all requests with the query parameter value b go to the backend service called backendserviceforprocessingoptionb these requirements are summarized in the following table request backend service http test mydomain com abtest a backendserviceforprocessingoptiona http test mydomain com abtest b backendserviceforprocessingoptionb to configure this in your global url map you can create the following settings match action pathmatchers routerules matchrules queryparametermatches name abtest pathmatchers routerules matchrules queryparametermatches exactmatch a pathmatchers routerules service backendserviceforprocessingoptiona pathmatchers routerules matchrules queryparametermatches name abtest pathmatchers routerules matchrules queryparametermatches exactmatch b pathmatchers routerules service backendserviceforprocessingoptionb for a configuration example see header based and parameter based routing routing requests to backends the backend for your traffic is determined by using a two phased approach the load balancer selects a backend service with backends the backends can be the following compute engine virtual machine vm instances in an unmanaged instance group compute engine vms in a managed instance group mig containers by means of a google kubernetes engine gke node in a zonal network endpoint group neg external backends outside of google cloud in an internet neg cloud storage in backend buckets app engine cloud run functions or cloud run services in a serverless neg the load balancer chooses a backend service based on rules defined in a global url map the backend service selects a backend instance based on policies defined in a global backend service when you configure routing you can choose between the following modes simple host and path testing by using pathrules advanced request testing by using routerules for each url map you can choose to use simple host and path rules or advanced host path and route rules the two modes are mutually exclusive each url map can contain only one mode or the other mode simple host and path rule in a simple host and path rule url maps work as described in the url map overview the following diagram shows the logical flow of a simple host and path rule figure 3 url map flow with a simple host and path rule a request is initially evaluated by using host rules a host is the domain specified by the request if the request host matches one of the entries in the hosts field the associated path matcher is used next the path matcher is evaluated path rules are evaluated on the longest path matches first basis and you can specify path rules in any order after the most specific match is found the request is routed to the corresponding backend service if the request does not match the default backend service is used a typical simple host and path rule might look something like the following where video traffic goes to video backend service and all other traffic goes to web backend service gcloud compute url maps describe ext https map defaultservice global backendservices web backend service hostrules hosts pathmatcher pathmap name ext https map pathmatchers defaultservice global backendservices web backend service name pathmap pathrules paths video video service global backendservices video backend service for a configuration example see host and path advanced host path and route rule advanced host path and route rules provide additional configuration options compared to simple host and path rules these options enable more advanced traffic management patterns and also modify some of the semantics for example route rules are executed in order rather than by using longest path matches first semantics as in the earlier simple host and path rule example you can configure advanced traffic management by using a global url map but instead of using pathmatchers pathrules you use pathmatchers routerules the following sections explain the advanced host path and route rule components host rules when a request reaches your load balancer the request s host field is evaluated against the hostrules defined in the url map each host rule consists of a list of one or more hosts and a single path matcher pathmatcher if no hostrules are defined the request is routed to the defaultservice for more information see hostrules and defaultservice in the global url map api documentation path matchers after a request matches a host rule the load balancer evaluates the path matcher corresponding to the host a path matcher is made up of the following components one or more path rules pathrules or route rules routerules a default rule that executes when no other backend services match the rule has the following mutually exclusive options a default service specifies the default backend service to route to when no other backend services match a default redirect specifies the url to redirect to when no other backend services match when the load balancer is configured for a default service it can additionally be configured to rewrite the url before sending the request to the default service for more information see pathmatchers pathmatchers pathrules and pathmatchers routerules in the global url map api documentation path rules path rules pathrules specify one or more url paths such as or video path rules are generally intended for the type of simple host and path based routing described previously for more information see pathrules in the global url map api documentation route rules a route rule routerules matches information in an incoming request and makes a routing decision based on the match route rules can contain a variety of different match rules matchrules and a variety of different route actions routeaction a match rule evaluates the incoming request based on the http s request s path headers and query parameters match rules support various types of matches for example prefix match as well as modifiers for example case insensitivity this enables you to for example send http s requests to a set of backends based on the presence of a custom defined http header for a detailed list of options supported by matchrules see matchrules in the global url map api documentation if you have multiple route rules the load balancer executes them in order which allows you to specify custom logic for matching routing and other actions within a given route rule when the first match is made the load balancer stops evaluating the match rules and any remaining match rules are ignored google cloud performs the following actions looks for the first match rule that matches the request stops looking at any other match rules applies the actions in the corresponding route actions route rules have several components as described in the following table route rule component api field name description priority priority a number from 0 through 2 147 483 647 that is 2 31 1 assigned to a route rule within a given path matcher to determine the order of route rule evaluation the highest priority is 0 the lowest priority is 2147483647 as an example a rule with priority 4 is evaluated before a rule with priority 25 the first rule that matches the request is applied priority numbers can have gaps they don t need to be contiguous you cannot create multiple rules with the same priority description description an optional description of up to 1 024 characters service service the full or partial url of the backend service resource to which traffic is directed if this rule is matched match rules matchrules one or more rules that are evaluated against the request these matchrules can match all or a subset of the request s http attributes such as the path http headers and query get parameters within a matchrule all matching criteria must be met for the routerule s routeactions to take effect if a routerule has multiple matchrules the routeactions of the routerule take effect when a request matches any of the routerule s matchrules route action routeaction allows you to specify a url rewrite action to take when the match rule criteria are met redirect action urlredirect you can configure an action to respond with an http redirect when the match rule criteria are met this field cannot be used in conjunction with a route action for more information see the following fields in the global url map api documentation routerules routerules priority routerules description routerules service routerules matchrules routerules routeaction routerules urlredirect match rules match rules matchrules match one or more attributes of a request and take actions specified in the route rule the following list provides some examples of request attributes that can be matched by using match rules host a host name is the domain name portion of a url for example the host name portion of the url http example net video hd is example net in the request the host name comes from the host header as shown in this example curl command where 10 1 2 9 is the load balanced ip address curl v http 10 1 2 9 video hd header host example com paths follow the host name for example images the rule can specify whether the entire path or only the leading portion of the path needs to match other http request parameters such as http headers which allow cookie matching as well as matching based on query parameters get variables note that regular expression matching for header values isn t supported...