Production Keep Developing! Templates Jinja Setup Standard Context Standard Filters Controlling Autoescaping Registering Filters Context Processors Testing Flask Applications The Application The Testing Test Logging In and Out Test Adding Messages Other Testing Tricks Faking Resources and Context Keeping the Context Around Accessing and Modifying Sessions Testing JSON APIs Testing CLI Commands Application Request Context Decorator Based Signal Subscriptions Core Signals Pluggable Views Basic Principle Method Hints Method Based Dispatching Decorating Views Method Views for APIs The Application Context Purpose

. . . . . . . . 86 1.14 The Application Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 1.15 The Request Context . . . . . . . . . . . . . . . . . . . . a request in order to stay threadsafe. This approach is convenient, but requires a valid request context for dependency injection or when attempting to reuse code which uses a value pegged to the request use the test_request_context() method to try out url_for(). test_request_context() tells Flask to behave as though it’s handling a request even while we use a Python shell. See Context Locals. from flask

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 5.4.2 Request & Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 5.4.3 WebSocket Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 5.4.2 Request & Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 5.4.3 WebSocket Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 5.4.2 Request & Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 5.4.3 WebSocket Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 5.4.2 Request & Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 5.4.3 WebSocket Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 5.4.2 Request & Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 5.4.3 WebSocket Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 5.4.2 Request & Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 5.4.3 WebSocket Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 5.4.2 Request & Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 5.4.3 WebSocket Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 5.4.2 Request & Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 5.4.3 WebSocket Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware components and hooks • Strict adherence to RFCs