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 new image resources to our collec- tion. We’ll tackle this functionality next. We’ll use TDD this time around, to demonstrate how to apply this particular testing strategy when developing a Falcon application

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 new image resources to our collec- tion. We’ll tackle this functionality next. We’ll use TDD this time around, to demonstrate how to apply this particular testing strategy when developing a Falcon application

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 new image resources to our collec- tion. We’ll tackle this functionality next. We’ll use TDD this time around, to demonstrate how to apply this particular testing strategy when developing a Falcon application

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 a URL add new image resources to our collection. We’ll tackle this functionality next. We’ll use TDD this time around, to demonstrate how to apply this particular testing strategy when developing a Falcon application

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 a URL add new image resources to our collection. We’ll tackle this functionality next. We’ll use TDD this time around, to demonstrate how to apply this particular testing strategy when developing a Falcon application

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 a URL add new image resources to our collection. We’ll tackle this functionality next. We’ll use TDD this time around, to demonstrate how to apply this particular testing strategy when developing a Falcon application

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 new image resources to our collec- tion. We’ll tackle this functionality next. We’ll use TDD this time around, to demonstrate how to apply this particular testing strategy when developing a Falcon application

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 a URL add new image resources to our collection. We’ll tackle this functionality next. We’ll use TDD this time around, to demonstrate how to apply this particular testing strategy when developing a Falcon application

with canonical dash-separated names. Parsing all the headers to create this dict is done the first time this attribute is accessed. This parsing can be costly, so unless you need all the headers in this HTTP_406 = '406 Not Acceptable' HTTP_407 = '407 Proxy Authentication Required' HTTP_408 = '408 Request Time-out' HTTP_409 = '409 Conflict' HTTP_410 = '410 Gone' HTTP_411 = '411 Length Required' HTTP_412 = '412 Implemented' HTTP_502 = '502 Bad Gateway' HTTP_503 = '503 Service Unavailable' HTTP_504 = '504 Gateway Time-out' HTTP_505 = '505 HTTP Version not supported' HTTP_511 = '511 Network Authentication Required'

with canonical dash-separated names. Parsing all the headers to create this dict is done the first time this attribute is accessed. This parsing can be costly, so unless you need all the headers in this HTTP_406 = '406 Not Acceptable' HTTP_407 = '407 Proxy Authentication Required' HTTP_408 = '408 Request Time-out' HTTP_409 = '409 Conflict' HTTP_410 = '410 Gone' HTTP_411 = '411 Length Required' HTTP_412 = '412 Implemented' HTTP_502 = '502 Bad Gateway' HTTP_503 = '503 Service Unavailable' HTTP_504 = '504 Gateway Time-out' HTTP_505 = '505 HTTP Version not supported' HTTP_511 = '511 Network Authentication Required'