Timeline for Why does the API lack (proper) HTTP cache control headers?
Current License: CC BY-SA 2.5
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 18, 2020 at 8:33 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jul 8, 2010 at 10:56 | comment | added | Steffen Opel |
Re 'Caching is hard': it sure is - thanks for taking the time to explain your argument. I still think you are missing the point here and there, e.g: ETag might not even need to get recomputed, see Jeffs answer for an example); CPU time can simply be reduced by big iron, while network bandwidth/latency can not; Cache-Control is providing exactly the freshness interval your are suggesting, albeit in a standardized way every framework understands already - you are free to ignore Cache-Control in your apps cache strategy as you please ;)
|
|
| Jul 8, 2010 at 2:24 | history | answered | Igor Zevaka | CC BY-SA 2.5 |