From: jakub-w@riseup.net
To: 51133@debbugs.gnu.org
Cc: levenson@mmer.org
Subject: bug#51133: [PATCH 1/1] Tolerate http response line without reason phrase
Date: Tue, 12 Oct 2021 10:01:03 +0200 [thread overview]
Message-ID: <87h7dmhdts.fsf@riseup.net> (raw)
In-Reply-To: <20211011070355.20408-1-levenson@mmer.org> (Alexey Abramov via's message of "Mon, 11 Oct 2021 09:03:55 +0200")
I don't think the reason phrase is optional, even though it can be just
a whitespace.
Even if I'm not mistaken, however, I don't see the reason for Guile not
to be able to parse the status line without a space at the end.
Aside from that consider a string "HTTP/1.1 ", which should be a bad
response because the status code should definitely be obligatory,
however it passes through the (and d0 d1) check after applying this
patch.
next prev parent reply other threads:[~2021-10-12 8:01 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 [this message]
2021-10-12 8:26 ` Alexey Abramov via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2021-10-12 9:11 ` tomas
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=87h7dmhdts.fsf@riseup.net \
--to=jakub-w@riseup.net \
--cc=51133@debbugs.gnu.org \
--cc=levenson@mmer.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).