From 89f0a41e8baefddf2c6962a8f0eee71dfd124d21 Mon Sep 17 00:00:00 2001 From: Rasmus Dahlberg Date: Thu, 9 Dec 2021 11:14:31 +0100 Subject: added issues --- issues/fix-http-status-405.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 issues/fix-http-status-405.md (limited to 'issues/fix-http-status-405.md') diff --git a/issues/fix-http-status-405.md b/issues/fix-http-status-405.md new file mode 100644 index 0000000..7a06288 --- /dev/null +++ b/issues/fix-http-status-405.md @@ -0,0 +1,24 @@ +**Title:** Fix HTTP status 405
+**Date:** 2021-12-09
+ +# Summary +Stop returning HTTP Status 405 or ensure that RFC 2616 is followed. + +# Description +When using HTTP GET for a POST endpoint or vice versa, HTTP status code 405 is +currently returned by sigsum-log-go. According to RFC 2616, an Allow header MUST +be included in the response. This issue requires figuring out what +sigsum-log-go should do: not return HTTP Status 405 or adhere to RFC 2616? + +Extract from RFC 2616: +``` +10.4.6 405 Method Not Allowed + +The method specified in the Request-Line is not allowed for the resource +identified by the Request-URI. The response MUST include an Allow header +containing a list of valid methods for the requested resource. +``` + +To find the relevant parts in the sigsum-log-go code, see the output of + + git grep StatusMethodNotAllowed -- cgit v1.2.3