From: Arun Isaac <arunisaac@systemreboot.net>
To: 30076@debbugs.gnu.org
Subject: bug#30076: [PATCH] web: Recognize JSON content type as text.
Date: Thu, 11 Jan 2018 11:01:17 +0530 [thread overview]
Message-ID: <20180111053117.4597-1-arunisaac@systemreboot.net> (raw)
* module/web/response.scm (text-content-type?): Recognize JSON content
type as text.
---
module/web/response.scm | 1 +
1 file changed, 1 insertion(+)
diff --git a/module/web/response.scm b/module/web/response.scm
index 06e1c6dc1..679304c4d 100644
--- a/module/web/response.scm
+++ b/module/web/response.scm
@@ -184,6 +184,7 @@ reason phrase for the response's code."
represents a textual type such as `text/plain'."
(let ((type (symbol->string type)))
(or (string-prefix? "text/" type)
+ (string-suffix? "/json" type)
(string-suffix? "/xml" type)
(string-suffix? "+xml" type))))
--
2.15.1
next reply other threads:[~2018-01-11 5:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 5:31 Arun Isaac [this message]
2018-01-31 3:31 ` bug#30076: [PATCH] web: Recognize JSON content type as text Mark H Weaver
2018-01-31 6:04 ` Mark H Weaver
2018-02-02 7:31 ` Arun Isaac
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=20180111053117.4597-1-arunisaac@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=30076@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).