)]}'
{
  "commit": "baff2cab3d404a7240c368d2c0b00e9f79ebf642",
  "tree": "173537501cec7dfc8d4229792dcf204e5cd19e1f",
  "parents": [
    "25ffc3b7737515f4c8992f961d14e9c12ef181b5"
  ],
  "author": {
    "name": "Roman Arutyunyan",
    "email": "arut@nginx.com",
    "time": "Mon Sep 11 15:32:31 2017 +0300"
  },
  "committer": {
    "name": "Roman Arutyunyan",
    "email": "arut@nginx.com",
    "time": "Mon Sep 11 15:32:31 2017 +0300"
  },
  "message": "Stream: relaxed next upstream condition (ticket #1317).\n\nWhen switching to a next upstream, some buffers could be stuck in the middle\nof the filter chain.  A condition existed that raised an error when this\nhappened.  As it turned out, this condition prevented switching to a next\nupstream if ssl preread was used with the TCP protocol (see the ticket).\n\nIn fact, the condition does not make sense for TCP, since after successful\nconnection to an upstream switching to another upstream never happens.  As for\nUDP, the issue with stuck buffers is unlikely to happen, but is still possible.\nSpecifically, if a filter delays sending data to upstream.\n\nThe condition can be relaxed to only check the \"buffered\" bitmask of the\nupstream connection.  The new condition is simpler and fixes the ticket issue\nas well.  Additionally, the upstream_out chain is now reset for UDP prior to\nconnecting to a new upstream to prevent repeating the client data twice.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "81a0891dea5030ba45a80e91925b19d8e0cc5ed1",
      "old_mode": 33188,
      "old_path": "src/stream/ngx_stream_proxy_module.c",
      "new_id": "a6b4f7e2eab0d5d2ef15f0c6fd49833be5807cbc",
      "new_mode": 33188,
      "new_path": "src/stream/ngx_stream_proxy_module.c"
    }
  ]
}