Github user MikeThomsen commented on a diff in the pull request: https://github.com/apache/nifi/pull/2150#discussion_r149336584 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/InvokeHTTP.java --- @@ -1093,6 +1133,19 @@ private Charset getCharsetFromMediaType(MediaType contentType) { return contentType != null ? contentType.charset(StandardCharsets.UTF_8) : StandardCharsets.UTF_8; } + /** + * Retrieve the directory in which OkHttp should cache responses. This method opts + * to use a temp directory to write the cache, which means that the cache will be written + * to a new location each time this processor is scheduled. + * + * Ref: https://github.com/square/okhttp/wiki/Recipes#response-caching + * + * @return the directory in which the ETag cache should be written + */ + private static File getETagCacheDir() { + return Files.createTempDir(); --- End diff -- @pvillard31 Since there is a configured size limit on the field, it should stick to a reasonable size since there is a sane default of 10MB. If a user is foolish enough to set that to 10GB, not our problem.
---