From 8edb6563b4f70e3b16518ef9f00a688e64aa7609 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= <zbyszek@in.waw.pl>
Date: Tue, 18 Dec 2018 15:16:26 +0100
Subject: [PATCH] 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.
---
 src/shared/json.c | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/src/shared/json.c b/src/shared/json.c
index c410b62008..59c4617592 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;