. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 URI Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 1.6. URI Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 1.6.3. URI Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Features Falcon tries to do as little as possible while remaining highly effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks (see also: falcon.API). Why are trailing slashes trimmed from req.path? Falcon normalizes incoming URI paths to simplify later processing and improve the predictability of application logic. In addition resource. 16 Chapter 6. Documentation Falcon Documentation, Release 1.1.0 Why are field names in URI templates restricted to certain characters? Field names are restricted to the ASCII characters in

Features Falcon tries to do as little as possible while remaining highly effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks (see also: falcon.API). Why are trailing slashes trimmed from req.path? Falcon normalizes incoming URI paths to simplify later processing and improve the predictability of application logic. In addition same resource. 5.1. Community Guide 15 Falcon Documentation, Release 0.3.0 Why are field names in URI templates restricted to certain characters? Field names are restricted to the ASCII characters in

Features Falcon tries to do as little as possible while remaining highly effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks large-scale deployments. Features • Highly-optimized, extensible code base • Intuitive routing via URI templates and REST-inspired resource classes • Easy access to headers and bodies through request and on_get() responder. Any URI parameters that you specify in your routes will be turned into corresponding kwargs and passed into the target responder as such. We’ll see how to specify URI parameters in a moment

Features Falcon tries to do as little as possible while remaining highly effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks (see also: falcon.API). Why are trailing slashes trimmed from req.path? Falcon normalizes incoming URI paths to simplify later processing and improve the predictability of application logic. In addition same resource. 5.1. Community Guide 15 Falcon Documentation, Release 1.0.0 Why are field names in URI templates restricted to certain characters? Field names are restricted to the ASCII characters in

Features Falcon tries to do as little as possible while remaining highly effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks Documentation, Release 1.2.0 Why are trailing slashes trimmed from req.path? Falcon normalizes incoming URI paths to simplify later processing and improve the predictability of application logic. In addition “/foo/bar/”. Requests coming in for either path will be sent to the same resource. Why are field names in URI templates restricted to certain characters? Field names are restricted to the ASCII characters in

Features Falcon tries to do as little as possible while remaining highly effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks large-scale deployments. Features • Highly-optimized, extensible code base • Intuitive routing via URI templates and REST-inspired resource classes • Easy access to headers and bodies through request and on_get() responder. Any URI parameters that you specify in your routes will be turned into corresponding kwargs and passed into the target responder as such. We’ll see how to specify URI parameters in a moment

on_get() responder. Any URI parameters that you specify in your routes will be turned into corresponding kwargs and passed into the target responder as such. We’ll see how to specify URI parameters in a moment you can see that the response headers were set correctly. Just for fun, go ahead and paste the above URI into your browser. The image should display correctly. Inspecting the application now returns: falcon-inspect-app reference to the kwarg dictionary Falcon creates for each request. params will contain the route’s URI template params and their values, if any. 46 Chapter 5. Documentation Falcon Documentation, Release

on_get() responder. Any URI parameters that you specify in your routes will be turned into corresponding kwargs and passed into the target responder as such. We’ll see how to specify URI parameters in a moment you can see that the response headers were set correctly. Just for fun, go ahead and paste the above URI into your browser. The image should display correctly. Inspecting the application now returns: falcon-inspect-app reference to the kwarg dictionary Falcon creates for each request. params will contain the route’s URI template params and their values, if any. 46 Chapter 5. Documentation Falcon Documentation, Release

on_get() responder. Any URI parameters that you specify in your routes will be turned into corresponding kwargs and passed into the target responder as such. We’ll see how to specify URI parameters in a moment you can see that the response headers were set correctly. Just for fun, go ahead and paste the above URI into your browser. The image should display correctly. Inspecting the application now returns: falcon-inspect-app reference to the kwarg dictionary Falcon creates for each request. params will contain the route’s URI template params and their values, if any. 46 Chapter 5. Documentation Falcon Documentation, Release