proper handling of unsupported request methods

[OpenStack Infra]

https://review.openstack.org/120914

Dear documentation bug triager. This bug was created here because we did not know how to map the project name "openstack/heat" to a launchpad project name. This indicates that the notify_impact config needs tweaks. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit 8a2e0aff98b54f73773fb2e35770e1c35ec460a9
Author: Miguel Grinberg <email address hidden>
Date: Thu Sep 11 03:47:54 2014 +0000

    proper handling of unsupported request methods

    This change adds support for responding to unsupported methods for all
    routes. Invoking a route with an unsupported request method returns a 405
    status code, and the response includes the 'Allow' header listing the
    request methods supported by the requested URL. The OPTIONS request method
    is also automatically supported for all URLs, with the response
    returning the 'Allow' header. The way routes are registered has been
    changed so that unsupported methods can be detected automatically.

    Change-Id: I2de28e0fc6cd35ed060395405aa3770b1dc73376
    Closes-Bug: 1367057
    APIImpact
    DocImpact

[Atsushi SAKAI (sakaia)]

This issue is already solved by following change set

Define the behavior for a 405 response
Change-Id: I31143ea0f7e6727b7f80f83dced10c68c44ffe1a
https://github.com/openstack/api-site/commit/21e820969752200d41ac38f6ef23f0f458b0bbe4