HTTP requests from users can reach the appropriate module/version/instance in two ways: A request with a URL that ends at the domain level can be routed according to App Engine's default address routing rules. Alternatively, you can include a dispatch file that routes specific URL patterns according to your own rules.
If you test your app using the
the available routing and dispatch features are slightly different.
To programmatically create URLs that work with both production and
development servers, use the
See routing in the development server
to learn more.
Routing via URL
You can target an HTTP request with varying degrees of specificity. In the following examples appspot.com can be replaced with your app's custom domain if you have one. The URL substrings "instance", "version", "module", and "app-id" represent application and module attributes that you have defined yourself.
These two address forms are guaranteed to reach their target (if it exists). They will never be intercepted and rerouted by a pattern in the dispatch file:
- Sends a request to the named module, version, and instance.
- Send the request to an available instance of the named module and version.
These address forms have a default routing behavior. Note that the default routing is overridden if there is a matching pattern in the dispatch file:
- Send the request to an available instance of the default version of the named module.
- Send the request to an available instance of the given version of the default module.
- Send the request to an available instance of the default version of the default module.
The default module is defined by explicitly giving a module the name "default," or by not including the name parameter in the module's config file. Requests that specify no module or an invalid module are routed to the default module. You can use the Admin Console to designate a default version for a module, when appropriate.
If a request matches the
app-id.appspot portion of the hostname, but includes
a module, version, or instance name that does not exist, then the request is
routed to the default version of the default module. Soft routing does not
apply to custom domains; requests to them will return a 404 if the
hostname is invalid.
Restricting access to a module
All modules are public by default. If you want to restrict access to a module, add the “login: admin” parameter to its handlers.
Routing with a dispatch file
For certain URLs (described above), you can create a dispatch file that overrides the routing rules. This lets you send incoming requests to a specific module based on the path or hostname in the URL. For example, say that you want to route mobile requests like
http://simple-sample.appspot.com/mobile/ to a mobile frontend, route worker requests like
http://simple-sample.appspot.com/work/ to a static backend, and serve all static content from the default module.
To do this you can create a custom routing with a
dispatch.xml file. The file should be placed in the
WEB-INF directory of the default module.
<?xml version="1.0" encoding="UTF-8"?> <dispatch-entries> <dispatch> <!-- Default module serves the typical web resources and all static resources. --> <url>*/favicon.ico</url> <module>default</module> </dispatch> <dispatch> <!-- Default module serves simple hostname request. --> <url>simple-sample.appspot.com/</url> <module>default</module> </dispatch> <dispatch> <!-- Send all mobile traffic to the mobile frontend. --> <url>*/mobile/*</url> <module>mobile-frontend</module> </dispatch> <dispatch> <!-- Send all work to the one static backend. --> <url>*/work/*</url> <module>static-backend</module> </dispatch> </dispatch-entries>
The dispatch file can contain up to 10 routing rules. When specifying the URL string, neither the hostname nor the path can be longer than 100 characters.
As you can see,
dispatch.xml includes support for glob characters. Glob characters can be used only before the hostname and at the end of the path. If you prefer general routing rules that match many possible requests, you could specify the following:
<!-- Send any path that begins with “simple-sample.appspot.com/mobile” to the mobile-frontend module. --> <url>simple-sample.appspot.com/mobile*</url> <module>mobile-frontend</module> <!-- Send any domain/sub-domain with a path that starts with “work” to the static backend module. --> <url>*/work*</url> <module>static-backend</module>
You can also write expressions that are more strict:
<!-- Matches the path "/fun", but not "/fun2" or "/fun/other" --> <url>*/fun</url> <module>mobile-frontend</module> <!-- Matches the hostname 'customer1.myapp.com', but not '1.customer1.myapp.com. --> <url>customer1.myapp.com/*</url> <module>static-backend</module>
Uploading the dispatch fileTo upload the dispatch file, use the appcfg update_dispatch command, and specify the war directory for the default module. Be sure that all the modules mentioned in the file have already been uploaded before using this command.
# cd to the war directory containing the default module appcfg.sh update_dispatch .
Routing in the development server
Discovering instance addresses
The development server creates all instances at startup. Note that at this time basic scaling instances are not supported on the development server. Every instance that is created is assigned its own port. The port assignments appear in the server's log message stream. Web clients can communicate with a particular instance by targeting its port. Only one instance (and port) is created for automatic scaled modules. It looks like this in the server log:
INFO: Module instance module2-auto is running at http://localhost:37251/
A unique port is assigned to each instance of a manual scaled module:
INFO: Module instance manualmodule instance 0 is running at http://localhost:43190/ INFO: Module instance manualmodule instance 1 is running at http://localhost:52642/
In addition, each manual scaled module is assigned one extra port so clients can access the module without specifying a specific instance. Requests to this port are automatically routed to one of the configured instances:
INFO: Module instance manualmodule is running at http://localhost:12361/
The following table shows how these modules can be called in the development server and in the App Engine environment:
|Module||Instance||Development Server Address||App Engine Address|