)]}'
{
  "commit": "54dc6a76ab467fc3bcafe929ac7e128e5b7f0438",
  "tree": "12599e7139d52e391e80871a18b27070952d2aaf",
  "parents": [
    "3f6f3d9ac0b9af037de08512b5a9d4cd01e0a276"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue May 25 15:17:41 2021 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue May 25 15:17:41 2021 +0300"
  },
  "message": "Resolver: fixed label types handling in ngx_resolver_copy().\n\nPreviously, anything with any of the two high bits set were interpreted\nas compression pointers.  This is incorrect, as RFC 1035 clearly states\nthat \"The 10 and 01 combinations are reserved for future use\".  Further,\nthe 01 combination is actually allocated for EDNS extended label type\n(see RFC 2671 and RFC 6891), not really used though.\n\nFix is to reject unrecognized label types rather than misinterpreting\nthem as compression pointers.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9b131723475e6dc4ef16e2dbcb25ded51f5294a4",
      "old_mode": 33188,
      "old_path": "src/core/ngx_resolver.c",
      "new_id": "12dab09ea8534d9dfca33b1aa98938c2e55c89cd",
      "new_mode": 33188,
      "new_path": "src/core/ngx_resolver.c"
    }
  ]
}