)]}'
{
  "commit": "27f64c6c245c6114f2a581a3f13c89ba72e1de36",
  "tree": "ef50b5f6c6693223082254529d7cad7592c76319",
  "parents": [
    "adae70470a4397d3e34c500677041e5f43114651"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Mon Jun 28 18:01:11 2021 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Mon Jun 28 18:01:11 2021 +0300"
  },
  "message": "Core: escaping of chars not allowed in URIs per RFC 3986.\n\nPer RFC 3986 only the following characters are allowed in URIs unescaped:\n\nunreserved    \u003d ALPHA / DIGIT / \"-\" / \".\" / \"_\" / \"~\"\ngen-delims    \u003d \":\" / \"/\" / \"?\" / \"#\" / \"[\" / \"]\" / \"@\"\nsub-delims    \u003d \"!\" / \"$\" / \"\u0026\" / \"\u0027\" / \"(\" / \")\"\n              / \"*\" / \"+\" / \",\" / \";\" / \"\u003d\"\n\nAnd \"%\" can appear as a part of escaping itself.  The following\ncharacters are not allowed and need to be escaped: %00-%1F, %7F-%FF,\n\" \", \"\"\", \"\u003c\", \"\u003e\", \"\\\", \"^\", \"`\", \"{\", \"|\", \"}\".\n\nNot escaping \"\u003e\" is known to cause problems at least with MS Exchange (see\nhttp://nginx.org/pipermail/nginx-ru/2010-January/031261.html) and in\nTomcat (ticket #2191).\n\nThe patch adds escaping of the following chars in all URI parts: \"\"\", \"\u003c\",\n\"\u003e\", \"\\\", \"^\", \"`\", \"{\", \"|\", \"}\".  Note that comments are mostly preserved\nto outline important characters being escaped.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7ed3463bbd2142b6810ef53b48cb5c18b7b9bcc8",
      "old_mode": 33188,
      "old_path": "src/core/ngx_string.c",
      "new_id": "98f270aca5b873204468f3271cadf03e08534150",
      "new_mode": 33188,
      "new_path": "src/core/ngx_string.c"
    }
  ]
}