pass control to # the given handler. app.add_error_handler(StorageError, StorageError.handle) # Proxy some things to another service; this example shows how you might # send parts of an API off to a legacy resources and responders would be impractical. For example, you might use a sink to create a smart proxy that forwards requests to one or more backend services. Parameters • sink (callable) – A callable request header field forwarded_host str – Original host request header as received by the first proxy in front of the application server. The following request headers are checked, in order of preference

pass control to # the given handler. app.add_error_handler(StorageError, StorageError.handle) # Proxy some things to another service; this example shows how you might # send parts of an API off to a resources and responders would be impractical. For example, you might use a sink to create a smart proxy that forwards requests to one or more backend services. Parameters: sink (callable) – A callable request header field forwarded_host str – Original host request header as received by the first proxy in front of the application server. The following request headers are checked, in order of preference

pass control to # the given handler. app.add_error_handler(StorageError, StorageError.handle) # Proxy some things to another service; this example shows how you might # send parts of an API off to a legacy to boost performance where it is most needed. If you have access to your load balancer or reverse proxy configuration, we recommend setting up path or subdomain- based rules to split requests between your resources and responders would be impractical. For example, you might use a sink to create a smart proxy that forwards requests to one or more backend services. Parameters • sink (callable) – A callable

pass control to # the given handler. app.add_error_handler(StorageError, StorageError.handle) # Proxy some things to another service; this example shows how you might # send parts of an API off to a legacy resources and responders would be impractical. For example, you might use a sink to create a smart proxy that forwards requests to one or more backend services. Parameters • sink (callable) – A callable request header field forwarded_host str – Original host request header as received by the first proxy in front of the application server. 58 Chapter 5. Documentation Falcon Documentation, Release 1

pass control to # the given handler. app.add_error_handler(StorageError, StorageError.handle) # Proxy some things to another service; this example shows how you might # send parts of an API off to a legacy resources and responders would be impractical. For example, you might use a sink to create a smart proxy that forwards requests to one or more backend services. Parameters • sink (callable) – A callable request header field forwarded_host str – Original host request header as received by the first proxy in front of the application server. 58 Chapter 5. Documentation Falcon Documentation, Release 1

pass control to # the given handler. app.add_error_handler(StorageError, StorageError.handle) # Proxy some things to another service; this example shows how you might # send parts of an API off to a legacy resources and responders would be impractical. For example, you might use a sink to create a smart proxy that forwards requests to one or more backend services. Parameters • sink (callable) – A callable request header field forwarded_host str – Original host request header as received by the first proxy in front of the application server. 58 Chapter 5. Documentation Falcon Documentation, Release 1

pass control to # the given handler. app.add_error_handler(StorageError, StorageError.handle) # Proxy some things to another service; this example shows how you might # send parts of an API off to a legacy pass control to # the given handler. app.add_error_handler(StorageError, StorageError.handle) # Proxy some things to another service; this example shows how you might # send parts of an API off to a legacy set_header('X-Request-ID', req.context.request_id) Note: If your app is deployed behind a reverse proxy that injects a request ID header, you can easily adapt this recipe to use the upstream ID rather than

pass control to # the given handler. app.add_error_handler(StorageError, StorageError.handle) # Proxy some things to another service; this example shows how you might # send parts of an API off to a legacy pass control to # the given handler. app.add_error_handler(StorageError, StorageError.handle) # Proxy some things to another service; this example shows how you might # send parts of an API off to a legacy set_header('X-Request-ID', req.context.request_id) Note: If your app is deployed behind a reverse proxy that injects a request ID header, you can easily adapt this recipe to use the upstream ID rather than

pass control to # the given handler. app.add_error_handler(StorageError, StorageError.handle) # Proxy some things to another service; this example shows how you might # send parts of an API off to a legacy pass control to # the given handler. app.add_error_handler(StorageError, StorageError.handle) # Proxy some things to another service; this example shows how you might # send parts of an API off to a legacy set_header('X-Request-ID', req.context.request_id) Note: If your app is deployed behind a reverse proxy that injects a request ID header, you can easily adapt this recipe to use the upstream ID rather than

pass control to # the given handler. app.add_error_handler(StorageError, StorageError.handle) # Proxy some things to another service; this example shows how you might # send parts of an API off to a legacy pass control to # the given handler. app.add_error_handler(StorageError, StorageError.handle) # Proxy some things to another service; this example shows how you might # send parts of an API off to a legacy set_header('X-Request-ID', req.context.request_id) Note: If your app is deployed behind a reverse proxy that injects a request ID header, you can easily adapt this recipe to use the upstream ID rather than