Cache the response lazily in memory, for repeated use.
Cache the response lazily in memory, for repeated use. Be careful when using this – keep in mind that this reponse could have been tailored for a particular request and won't work for a different request (e.g. it could be a 304 Not Modified response due to the request's If-Modified-Since header)
A new Response which caches this response's body in memory.
Terminate the response, if it's still writing.
Terminate the response, if it's still writing.
Produce a memory-mapped version of this response.
Produce a memory-mapped version of this response. NOTE: This will leak, because it can't be unmapped. Only do this if you intend to keep the memory-mapped response for the duration of your app.
Like mmap, but returns a managed resource that closes the file channel after use.
Size of response body (excluding headers)
Size of response body (excluding headers)
Add cache-control header enabling modification time checking on the client
Add cache-control header enabling modification time checking on the client