Cachebusters should change between passes
Opened this issue · 1 comments
There is a command-line option that allows for doing multiple "passes", so that any directives that fail in one pass will be re-tested in the next pass. There is a bug with this currently where if cachebusting is enabled, the cachebuster does not change between passes, but it should.
It has long been my suspicion that part of the reason --passes=2 was generally successful was due to this accidental (mis)feature. In my mind, this issue dovetails with #16. For particularly expensive URLs such as XML sitemaps, whether those URLs are serving the content and the appropriate status code is probably more important than whether they're being freshly generated by the origin. If this issue is resolved and we more aggressively cache-bust between passes, maybe these more expensive URLs could be marked as not to be cache-busted.