From b09d20111227be5e6d5126ec905b44a7a4e96b0d Mon Sep 17 00:00:00 2001 From: Rasmus Dahlberg Date: Wed, 30 Mar 2022 22:45:46 +0200 Subject: move issues to a common pad --- issues/fix-http-status-405.md | 24 ------------------------ 1 file changed, 24 deletions(-) delete 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 deleted file mode 100644 index 7a06288..0000000 --- a/issues/fix-http-status-405.md +++ /dev/null @@ -1,24 +0,0 @@ -**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