Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

An interesting approach would be to delete the original data, but issue an ETag to leverage browser caching. If the original user rerequests the page while it's still in the browser's persistent cache, the server can simply return a 304 Not Modified, and the user still sees their data. Anyone else, though, is SOL.


Anyone else, except for people behind the same caching web proxy...


Presumably the entire thing is served over HTTPS, making this a non-issue.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: