From: Maxime Devos <maximedevos@telenet.be>
To: Ryan Raymond <rjraymond@oakland.edu>,
"guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: RE: Custom HTTP methods in web module
Date: Sat, 23 Mar 2024 19:50:06 +0100 [thread overview]
Message-ID: <20240323195006.2Jq52C00K5DtEJR01Jq6FE@laurent.telenet-ops.be> (raw)
In-Reply-To: <CAGvJ-HSOn7npYqfMOb1shRMf5jJz5xeCxeFH_4iUZi9KmdMvPQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
(else (bad-request "Invalid method: ~a" (substring str start end)))))
Another problem with the old implementation – AFAICT, this does a “400 Bad Request”. However, at least when the syntax/grammar/... is correct, it should be a 501 instead.
>An origin server that receives a request method that is unrecognized or not implemented SHOULD respond with the 501 (Not Implemented) status code. An origin server that receives a request method that is recognized and implemented, but not allowed for the target resource, SHOULD respond with the 405 (Method Not Allowed) status code.
Given the proposal to (in this procedure) allow all methods (at least all grammatical methods) in a new implementation, it seems this won’t be this method’s responsibility anymore, though.
Best regards,
Maxime Devos
[-- Attachment #2: Type: text/html, Size: 3207 bytes --]
next prev parent reply other threads:[~2024-03-23 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 22:14 Custom HTTP methods in web module Ryan Raymond
2024-03-23 12:49 ` Maxime Devos
2024-03-23 18:50 ` Maxime Devos [this message]
[not found] ` <CAGvJ-HS5Laqd7=v=WCn4-2zUurXVZcKDFA2+MmNPO-cZO6iUJg@mail.gmail.com>
2024-03-24 13:57 ` Maxime Devos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240323195006.2Jq52C00K5DtEJR01Jq6FE@laurent.telenet-ops.be \
--to=maximedevos@telenet.be \
--cc=guile-devel@gnu.org \
--cc=rjraymond@oakland.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).