)]}'
{
  "commit": "e814d33900992e034a8c3ddec2c65463c5206090",
  "tree": "dae1062d5eb6642c724d3204d442e67c9b20efa4",
  "parents": [
    "f4f9adf618cd85d330a896e1f721f3aa78d2409d"
  ],
  "author": {
    "name": "Michael Brown",
    "email": "mcb30@ipxe.org",
    "time": "Thu Jan 13 14:53:36 2022 +0000"
  },
  "committer": {
    "name": "Michael Brown",
    "email": "mcb30@ipxe.org",
    "time": "Thu Jan 13 15:03:22 2022 +0000"
  },
  "message": "[uri] Allow for relative URIs that include colons within the path\n\nRFC3986 allows for colons to appear within the path component of a\nrelative URI, but iPXE will currently parse such URIs incorrectly by\ninterpreting the text before the colon as the URI scheme.\n\nFix by checking for valid characters when identifying the URI scheme.\nDeliberately deviate from the RFC3986 definition of valid characters\nby accepting \"_\" (which was incorrectly used in the iPXE-specific\n\"ib_srp\" URI scheme and so must be accepted for compatibility with\nexisting deployments), and by omitting the code to check for\ncharacters that are not used in any URI scheme supported by iPXE.\n\nReported-by: Ignat Korchagin \u003cignat@cloudflare.com\u003e\nSigned-off-by: Michael Brown \u003cmcb30@ipxe.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a0f79e9ec11e1fda13774df3f45e3990901389e6",
      "old_mode": 33188,
      "old_path": "src/core/uri.c",
      "new_id": "b82472ef03b3fb359d121ef45e9a6e920505f5b8",
      "new_mode": 33188,
      "new_path": "src/core/uri.c"
    },
    {
      "type": "modify",
      "old_id": "929ab3632502e0f722dc496b0049c835af492f3e",
      "old_mode": 33188,
      "old_path": "src/tests/uri_test.c",
      "new_id": "338f479cd3778d3f20e0a526c9029145f847fc03",
      "new_mode": 33188,
      "new_path": "src/tests/uri_test.c"
    }
  ]
}