From: Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Date: Tue, 18 Dec 2018 14:16:26 +0000 (+0100)
Subject: json: do not unescape slashes
X-Git-Tag: v240~24^2
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=8edb6563b4f70e3b16518ef9f00a688e64aa7609;p=thirdparty%2Fsystemd.git

json: do not unescape slashes

Apparently this originated in PHP, so the json output could be directly
embedded in HTML script tags.
See https://stackoverflow.com/questions/1580647/json-why-are-forward-slashes-escaped.

Since the output of our tools is not intended directly for web page generation,
let's not do this unescaping. If needed, the consumer can always do escaping as
appropriate for the target format.
---

diff --git a/src/shared/json.c b/src/shared/json.c
index c410b620084..59c4617592c 100644
--- a/src/shared/json.c
+++ b/src/shared/json.c
@@ -1381,10 +1381,6 @@ static int json_format(FILE *f, JsonVariant *v, JsonFormatFlags flags, const cha
                                 fputs("\\\\", f);
                                 break;
 
-                        case '/':
-                                fputs("\\/", f);
-                                break;
-
                         case '\b':
                                 fputs("\\b", f);
                                 break;