Simple API modeling through centralized RESTful routing Highly-optimized, extensible code base Easy access to headers and bodies through request and response objects DRY request processing via middleware Simple API modeling through centralized RESTful routing Highly-optimized, extensible code base Easy access to headers and bodies through request and response objects DRY request processing via middleware input stream; by default Falcon does not spool or decode request data, instead giving you direct access to the incoming binary stream provided by the WSGI server. Note the use of falcon.HTTP_201 for setting

Simple API modeling through centralized RESTful routing Highly-optimized, extensible code base Easy access to headers and bodies through request and response objects DRY request processing via middleware Simple API modeling through centralized RESTful routing Highly-optimized, extensible code base Easy access to headers and bodies through request and response objects DRY request processing via middleware input stream; by default Falcon does not spool or decode request data, instead giving you direct access to the incoming binary stream provided by the WSGI server. Note the use of falcon.HTTP_201 for setting

REST-inspired resource classes No reliance on magic globals for routing and state management Easy access to headers and bodies through request and response classes DRY request processing via middleware input stream; by default Falcon does not spool or decode request data, instead giving you direct access to the incoming binary stream provided by the WSGI server. Note the use of falcon.HTTP_201 for setting classes contain convenient attributes for reading and setting common headers, but you can always access any header by name with the req.get_header() and resp.set_header() methods. Take a moment to run

REST-inspired resource classes No reliance on magic globals for routing and state management Easy access to headers and bodies through request and response classes DRY request processing via middleware input stream; by default Falcon does not spool or decode request data, instead giving you direct access to the incoming binary stream provided by the WSGI server. Note the use of falcon.HTTP_201 for setting classes contain convenient attributes for reading and setting common headers, but you can always access any header by name with the req.get_header() and resp.set_header() methods. Take a moment to run

API modeling through centralized RESTful routing • Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware API modeling through centralized RESTful routing • Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware input stream; by default Falcon does not spool or decode request data, instead giving you direct access to the incoming binary stream provided by the WSGI server. Note the use of falcon.HTTP_201 for setting

API modeling through centralized RESTful routing • Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware API modeling through centralized RESTful routing • Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware input stream; by default Falcon does not spool or decode request data, instead giving you direct access to the incoming binary stream provided by the WSGI server. Note the use of falcon.HTTP_201 for setting

REST-inspired resource classes • No reliance on magic globals for routing and state management • Easy access to headers and bodies through request and response classes • DRY request processing via middleware input stream; by default Falcon does not spool or decode request data, instead giving you direct access to the incoming binary stream provided by the WSGI server. Note the use of falcon.HTTP_201 for setting classes contain convenient attributes for reading and setting common headers, but you can always access any header by name with the req.get_header() and resp.set_header() methods. Take a moment to run

API modeling through centralized RESTful routing • Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware API modeling through centralized RESTful routing • Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware input stream; by default Falcon does not spool or decode request data, instead giving you direct access to the incoming binary stream provided by the WSGI server. Note the use of falcon.HTTP_201 for setting

API modeling through centralized RESTful routing • Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware API modeling through centralized RESTful routing • Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware input stream; by default Falcon does not spool or decode request data, instead giving you direct access to the incoming binary stream provided by the WSGI server. Note the use of falcon.HTTP_201 for setting

API modeling through centralized RESTful routing • Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware API modeling through centralized RESTful routing • Highly-optimized, extensible code base • Easy access to headers and bodies through request and response objects • DRY request processing via middleware input stream; by default Falcon does not spool or decode request data, instead giving you direct access to the incoming binary stream provided by the WSGI server. Note the use of falcon.HTTP_201 for setting