From 28348f511feeccda88af47896455b878ab981f6e Mon Sep 17 00:00:00 2001 From: Randall Schmidt Date: Thu, 10 Jun 2021 12:11:04 -0400 Subject: [PATCH] update readme --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e65e328..88560a2 100644 --- a/README.md +++ b/README.md @@ -87,7 +87,7 @@ Returns the headers as an object of `{ "key": "value" }` pairs, same as [node-fe This module supports streams like [node-fetch](https://www.npmjs.com/package/node-fetch) does, but with a couple of caveats you should be aware of if you want to use streams. 1. Response bodies are always read into memory even if you stream them to disk. That means if you need to stream large responses that don't fit into RAM, this module may be unsuitable. -2. When streaming a request body with fs.ReadStream, the cache key is generated based only on the path of the stream, not its content. That means if you stream `image.png` twice, you will get a cached response the second time, **even if the content of image.png has changed**. This module may be unsuitable if you need to stream files in requests and the content of those files can change. +2. When streaming a request body with fs.ReadStream, the cache key is generated based only on the path of the stream, not its content. That means if you stream `/my/desktop/image.png` twice, you will get a cached response the second time, **even if the content of image.png has changed**. This module may be unsuitable if you need to stream files in requests and the content of those files can change. ## Bugs / Help / Feature Requests / Contributing