From: <tomas@tuxteam.de>
To: 51133@debbugs.gnu.org
Subject: bug#51133: [PATCH 1/1] Tolerate http response line without reason phrase
Date: Tue, 12 Oct 2021 11:11:43 +0200 [thread overview]
Message-ID: <20211012091143.GA32113@tuxteam.de> (raw)
In-Reply-To: <875yu2r6mp.fsf@delta.lan>
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
On Tue, Oct 12, 2021 at 10:26:22AM +0200, Alexey Abramov via Bug reports for GUILE, GNU's Ubiquitous Extension Language wrote:
> Hi,
>
> I agree that it is not a complient http response,
According to The Book [1] ;-) there should be at least one
space (SP) (as far as I understand this is really a true
honest space, Unicode codepoint 32. It is /not/ part of the
message (aka "reason phrase") , but a separator. The rule
is:
status-line = HTTP-version SP status-code SP reason-phrase CRLF
The reason phrase itself can contain whatever funny whitespace
it wants:
reason-phrase = *( HTAB / SP / VCHAR / obs-text )
and it /can/ be empty.
That said I'd agree that it makes sense to tolerate a missing
SP there. The legal minimum seems thus to be
HTTP-version SP status-code SP CRLF
> but unfortunately I
> came across with some http services (redfish, cimc from Cisco )
uh-oh. All bets are off, then ;-)
> where they don't put a reason phrase.
That would be OK, but they also eat the mandatory separator space
before the empty reason phrase. Bad folks, bad ;-)
As an onlooker I haven't much to say, but I think you are right
(but not Cisco :)
Cheers
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2021-10-12 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 7:03 bug#51133: [PATCH 1/1] Tolerate http response line without reason phrase Alexey Abramov via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2021-10-12 8:01 ` jakub-w
2021-10-12 8:26 ` Alexey Abramov via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2021-10-12 9:11 ` tomas [this message]
2021-10-12 10:03 ` jakub-w
2021-10-12 14:35 ` Alexey Abramov via Bug reports for GUILE, GNU's Ubiquitous Extension Language
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=20211012091143.GA32113@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=51133@debbugs.gnu.org \
/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).