)]}'
{
  "commit": "c60aebb10d5aa071d3e1456ef3ca949860213188",
  "tree": "84bc628107bacf26eb237d6a553509003c42e8da",
  "parents": [
    "96e2fff434e48d0b9e1c1f2c09be48da1a5cad24"
  ],
  "author": {
    "name": "Jay Doane",
    "email": "jaydoane@apache.org",
    "time": "Tue Aug 10 15:04:12 2021 -0700"
  },
  "committer": {
    "name": "Jay Doane",
    "email": "jaydoane@apache.org",
    "time": "Tue Aug 10 16:12:40 2021 -0700"
  },
  "message": "Fix allowed method for ddoc update function\n\nThe semantics of PUT [1] are arguably incorrect for executing an\nupdate function on a specified document, since nothing is being\ncreated or updated. Also it\u0027s not clear why it would be different from\nthe POST used for executing an update function for `null` document. [2]\n\nAdditionally, the example code-block in this section uses POST:\n\n        POST /recipes/_design/recipe/_update/ingredients/SpaghettiWithMeatballs HTTP/1.1\n\nAll which lead me to believe that the PUT is a typo.\n\nThe actual behavior of CouchDB doesn\u0027t help here, since it currently\naccepts any method whatsoever:\n\n$ curl -v -u adm localhost:15984/db-1/_design/ddoc/_update/change -X BOGUS\n\n\u003e BOGUS /db-1/_design/bar/_update/change HTTP/1.1\n\u003e\n\u003c HTTP/1.1 200 OK\n\u003c content-length: 11\n\u003c content-type: text/html; charset\u003dutf-8\n\u003c\n* Connection #0 to host localhost left intact\nEmpty World* Closing connection 0\n\n[1] https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html\n[2] https://docs.couchdb.org/en/latest/api/ddoc/render.html#post--db-_design-ddoc-_update-func\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d7c7b0ec9c54e2f5edff175b18c2f10bcf826f1e",
      "old_mode": 33188,
      "old_path": "src/api/ddoc/render.rst",
      "new_id": "8324bcd4cc5a4314b01a6d6544d48fd18a92acc5",
      "new_mode": 33188,
      "new_path": "src/api/ddoc/render.rst"
    }
  ]
}
