)]}'
{
  "commit": "6614afa213b94d6dbcd1b85128bc0da576dbf16a",
  "tree": "d71eed9639e5127f8898bdf0a24706abb004ea3d",
  "parents": [
    "d4f0bca583b17894f1ea468d63f3b250d8d5c5ae"
  ],
  "author": {
    "name": "Ruslan Ermilov",
    "email": "ru@nginx.com",
    "time": "Mon Oct 17 14:27:45 2016 +0300"
  },
  "committer": {
    "name": "Ruslan Ermilov",
    "email": "ru@nginx.com",
    "time": "Mon Oct 17 14:27:45 2016 +0300"
  },
  "message": "Upstream: don\u0027t consider default_port when matching upstreams.\n\nThe only thing that default_port comparison did in the current\ncode is prevented implicit upstreams to the same address/port\nfrom being aliased for http and https, e.g.:\n\n\tproxy_pass http://10.0.0.1:12345;\n\tproxy_pass https://10.0.0.1:12345;\n\nThis is inconsistent because it doesn\u0027t work for a similar case\nwith uswgi_pass:\n\n\tuwsgi_pass uwsgi://10.0.0.1:12345;\n\tuwsgi_pass suwsgi://10.0.0.1:12345;\n\nor with an explicit upstream:\n\n\tupstream u {\n\t    server 10.0.0.1:12345;\n\t}\n\n\tproxy_pass http://u;\n\tproxy_pass https://u;\n\nBefore c9059bd5445b, default_port comparison was needed to\ndifferentiate implicit upstreams in\n\n\tproxy_pass http://example.com;\n\nand\n\n\tproxy_pass https://example.com;\n\nas u-\u003eport was not set.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "828b7d726cb3dcb3c6b0ed7bcf1ddf7b94ba5418",
      "old_mode": 33188,
      "old_path": "src/http/ngx_http_upstream.c",
      "new_id": "6e5cab8ed8b89cd40347afe4d14659afe2055dc7",
      "new_mode": 33188,
      "new_path": "src/http/ngx_http_upstream.c"
    }
  ]
}