mitm-cache record doesn't log HEAD requests in its JSON output. This means that successful HEAD requests at record time become 404 errors at replay time. This can break mitm-cache-backed builds for some Gradle projects like spock. Gradle sometimes makes a HEAD request and decides not to download a file. If the URL is missing from the cache during a subsequent replay, Gradle treats a 404 response to its HEAD request as an error.
When mitm-cache encounters a HEAD request while recording, it'd be useful if it could make the corresponding GET request to ensure that the download is logged.
mitm-cache recorddoesn't log HEAD requests in its JSON output. This means that successful HEAD requests at record time become 404 errors at replay time. This can break mitm-cache-backed builds for some Gradle projects like spock. Gradle sometimes makes a HEAD request and decides not to download a file. If the URL is missing from the cache during a subsequent replay, Gradle treats a 404 response to its HEAD request as an error.When mitm-cache encounters a HEAD request while recording, it'd be useful if it could make the corresponding GET request to ensure that the download is logged.