Fix memory access violation in NGINX 1.13.10

[travisspencer]

Due to what seems like a change in NGINX 1.13.10, the cached request buffer is freed after the first use. Consequently, the first request with some token where the cache is empty succeeds (when the cache is enabled) . The next with the same token, however, fails because the buffer has been freed. The result is a segfault.