Many other services send explicit Cache-Control max-age with different value depending on rev parameter existence. E.g. thumbnail service.
The open/log (History) service does not (in my setup) which means that it might get the fallback max-age=36000 that we set in order to cache rweb static files.
Header setifempty Cache-Control "max-age=36000"
Traditionally (before setifempty) the open/log service avoided cache problems via the "recent date heuristics" in the browsers because the "Date" response header is always set to when response is generated on the server. (this is my assumption why it has been working without Cache-Control)