alficles commented on pull request #6017: URL: https://github.com/apache/trafficcontrol/pull/6017#issuecomment-880065143
> if I make a change, I might not be able to read that change back for however long the cache time is That's kind of how HTTP works in the general case. If you want write-read consistency, you can get that by setting `Cache-Control: max-age` to the difference between your write and your read time. And if you're reading immediately after writing, writers should be sending `Cache-Control: no-cache`. The fact that a naive cache-control happens to work at the moment is mostly an accident and is only true when there aren't caching proxies for those endpoints in front of TO. I don't think I see correct support for `max-age` in the PR, though. @rob05c , that's probably an important feature. `no-cache` is fine for immediate reads, which might be the common case, but it'd be nice to support it completely. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
