Hacker News Reader

You get a 304 because your browser tells the server what it has cached, and the server says "nothing changed, use that". In browsers you can bypass the cache by using Ctrl-F5, or in the developer tools you can usually disable caching while they're open. Doing so shows that the server is doing the right thing.

Your LLM prompt and response are worthless.

View on HN

When Chrome serves a cached page, like when you click a on this page and then navitate back or hit F5, it shows it like this:

Request URL: https://news.ycombinator.com/item?id=46196076

Request Method: GET

Status Code: 200 OK (from disk cache)

I just thought that it would be worthwhile investigating in that direction.

That's a different situation. The browser decides what to do depending on the situation and what was communicated about caching. Sometimes it sends a request to the server along with information about what it already has. Then it can get back a 304. Other times it already knows the cached data is fine, so it doesn't send a request to the server in the first place. The developer tools show this as a cached 200.

Got it, thanks for explaining.

Reply on news.ycombinator.com