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 • Idiomatic HTTP error responses 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 • Idiomatic HTTP error responses Let’s see what happens when a different method is requested: $ http PUT localhost:8000/images This time you should get back 405 Method Not Allowed, since the resource does not support the PUT method. Note

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 • Idiomatic HTTP error responses 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 • Idiomatic HTTP error responses Let’s see what happens when a different method is requested: $ http PUT localhost:8000/images This time you should get back 405 Method Not Allowed, since the resource does not support the PUT method. Note

management • Easy access to headers and bodies through request and response classes • DRY request processing via middleware components and hooks • Idiomatic HTTP error responses • Straightforward exception Let’s see what happens when a different method is requested: $ http PUT localhost:8000/images This time you should get back 405 Method Not Allowed, since the resource does not support the PUT method. Note of the application is centralized. This makes it easier to reason about and maintain the API over time. • The use of resource classes maps somewhat naturally to the REST architectural style, in which

management • Easy access to headers and bodies through request and response classes • DRY request processing via middleware components and hooks • Idiomatic HTTP error responses • Straightforward exception Let’s see what happens when a different method is requested: $ http PUT localhost:8000/images This time you should get back 405 Method Not Allowed, since the resource does not support the PUT method. Note of the application is centralized. This makes it easier to reason about and maintain the API over time. • The use of resource classes maps somewhat naturally to the REST architectural style, in which

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 • Idiomatic HTTP error responses 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 • Idiomatic HTTP error responses Let’s see what happens when a different method is requested: $ http PUT localhost:8000/images This time you should get back 405 Method Not Allowed, since the resource does not support the PUT method. Note

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 • Idiomatic HTTP error responses 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 • Idiomatic HTTP error responses Let’s see what happens when a different method is requested: $ http PUT localhost:8000/images This time you should get back 405 Method Not Allowed, since the resource does not support the PUT method. Note

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 • Idiomatic HTTP error responses 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 • Idiomatic HTTP error responses Let’s see what happens when a different method is requested: $ http PUT localhost:8000/images This time you should get back 405 Method Not Allowed, since the resource does not support the PUT method. Note

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 • Idiomatic HTTP error responses 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 • Idiomatic HTTP error responses Let’s see what happens when a different method is requested: $ http PUT localhost:8000/images This time you should get back 405 Method Not Allowed, since the resource does not support the PUT method. Note

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 • Idiomatic HTTP error responses 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 • Idiomatic HTTP error responses Let’s see what happens when a different method is requested: $ http PUT localhost:8000/images This time you should get back 405 Method Not Allowed, since the resource does not support the PUT method. Note

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 • Idiomatic HTTP error responses 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 • Idiomatic HTTP error responses Let’s see what happens when a different method is requested: $ http PUT localhost:8000/images This time you should get back 405 Method Not Allowed, since the resource does not support the PUT method. Note