Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

New cached responses generated for identical request

See original GitHub issue

Talkback keeps generating new cached responses after server restart even though the requests are identical. I thought the expected behaviour was that identical requests would cause the cached response to be returned.

I’m guessing differences in meta and res shouldn’t cause a new cached response to be generated?

Issue Analytics

State:
Created 5 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

2reactions

ijpiantanidacommented, May 2, 2018

You’re totally right @roypa! Thank you so much.

I just released 1.2.0 that fixes this issue.

0reactions

hanshenrikcommented, May 3, 2018

Yes, great stuff! Thanks!

Top Results From Across the Web

HTTP caching - MDN Web Docs

The HTTP cache stores a response associated with a request and reuses the stored response for subsequent requests.

Response caching in ASP.NET Core - Microsoft Learn

A client can make requests with a no-cache header value and force the server to generate a new response for every request.

Prevent unnecessary network requests with the HTTP Cache

First, the browser checks the HTTP Cache and finds the previous response. Unfortunately, the browser can't use the previous response because the ...

HTTP/1.1: Caching in HTTP

Servers MUST NOT depend on clients being able to choose deterministically between responses generated during the same second, if their expiration times overlap....

Cache filter — envoy 1.25.0-dev-a95421 documentation

Cached responses can be identified by having an age header. Validated responses can be identified by having a generation date older than the ......