)]}'
{
  "commit": "802cacf34f2db9111becb4f0d3aa00460df13a19",
  "tree": "6043bc8fa7e3dc272efeae8d8594076ee5f30d25",
  "parents": [
    "de56f726e163e99128ff93a04d74a8461f5a724b"
  ],
  "author": {
    "name": "Vita Batrla",
    "email": "vitezslav.batrla@oracle.com",
    "time": "Fri Mar 18 22:02:50 2022 +0100"
  },
  "committer": {
    "name": "Tomas Mraz",
    "email": "tomas@openssl.org",
    "time": "Thu May 05 13:36:23 2022 +0200"
  },
  "message": "s_client -proxy / -starttls shouldn\u0027t be mutually exclusive\n\nThe option -proxy of openssl s_client works fine. The option\n-starttls also works fine. However, try putting both of them\non command line. It breaks, these options don\u0027t work together.\n\nThe problem is that -proxy option is implemented using starttls_proto\n(the option parsing code sets it to PROTO_CONNECT) and -starttls option\noverwrites the same variable again based on argument value.\n\nThe suggested fix is to independently handle -proxy option before\n-starttls so the s_client can connect through HTTP proxy server and\nthen use STARTTLS command.\n\nReviewed-by: Matt Caswell \u003cmatt@openssl.org\u003e\nReviewed-by: Tomas Mraz \u003ctomas@openssl.org\u003e\n(Merged from https://github.com/openssl/openssl/pull/17925)\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e4972a2ec719d2961d0d2163e8a45b611b267d20",
      "old_mode": 33188,
      "old_path": "apps/s_client.c",
      "new_id": "1ed5f753e6dc9e63eedfe040f3b9b123386cceae",
      "new_mode": 33188,
      "new_path": "apps/s_client.c"
    }
  ]
}