Currently if a wrong HTTP method is used, metad returns just 404. Instead, 405 should be returned, including the allowed methods.
While the actual read/write functionality hasn't been implemented yet, this is the correct thing to do anyway, and helps when developing metad/os scripts further. Petr Pudlak (2): Refactor error404 in metad using OverloadedStrings Let metad report if a wrong method is used for read/write cabal/ganeti.template.cabal | 1 + src/Ganeti/Metad/WebServer.hs | 19 ++++++++++++++++--- 2 files changed, 17 insertions(+), 3 deletions(-) -- 2.2.0.rc0.207.ga3a616c
