)]}'
{
  "commit": "564c9c8291dc9ebba82ab9fd606f156cedc346c0",
  "tree": "2da550bde1c2ef9fe537433d37241af1e3c222e5",
  "parents": [
    "f841ffeb361c59633afe63135ed3453e1a54ef23"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue May 25 15:17:50 2021 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue May 25 15:17:50 2021 +0300"
  },
  "message": "Resolver: explicit check for compression pointers in question.\n\nSince nginx always uses exactly one entry in the question section of\na DNS query, and never uses compression pointers in this entry, parsing\nof a DNS response in ngx_resolver_process_response() does not expect\ncompression pointers to appear in the question section of the DNS\nresponse.  Indeed, compression pointers in the first name of a DNS response\nhardly make sense, do not seem to be allowed by RFC 1035 (which says\n\"a pointer to a prior occurance of the same name\", note \"prior\"), and\nwere never observed in practice.\n\nAdded an explicit check to ngx_resolver_process_response()\u0027s parsing\nof the question section to properly report an error if compression pointers\nnevertheless appear in the question section.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9ce53b930f74cd223d2d811c0050bc7d51085ce5",
      "old_mode": 33188,
      "old_path": "src/core/ngx_resolver.c",
      "new_id": "58d5f3ec45dc4984c2b1fd7bd5ff29ff98ca67a8",
      "new_mode": 33188,
      "new_path": "src/core/ngx_resolver.c"
    }
  ]
}