[tldoc] viewvc shows latest changes only when a new browser window is opened

[Carlos]

On Tue, Mar 19, 2019 at 05:02:12PM -0600, Karl Berry wrote:

>and make a commit to that file, and then hit "Reload" in my browser
>(seamonkey on centos in this case, though I surmise any normal Unixish
>browser would be the same), the change appears right away, as expected.
>

Karl just wanted to let you know, that the above 's not
dissimilar from what I did (except of course, the browser in
this use case, and the system that powers it behind it).
Then I went ahead and changed to the top level directory and
back again to the subdirectory shortly after, where the
changes occurred. And that's when I noticed that no matter
what I did in my end by reloading it, it would still show
the unmodified changes.

>
>Neither viewvc, nor tug's web server, have any way to know or care
>whether you are refreshing in an existing window or starting a new
>window. Only your system knows that. -k
>

I wasn't implying so much as the server itself... but perhaps more on
the way the web interface is set when I referred to the
'settings' earlier.

According to the viewvc conf file there's a line that reads:


## http_expiration_time: Expiration time (in seconds) for cacheable
## pages served by ViewVC.  Note that in most cases, a cache aware
## client will only revalidate the page after it expires (using the
## If-Modified-Since and/or If-None-Match headers) and that browsers
## will also revalidate the page when the reload button is pressed.
## Set to 0 to disable the transmission of these caching headers.
##
#http_expiration_time = 600

https://github.com/viewvc/viewvc/blob/master/conf/viewvc.conf.dist

And this

## show_roots_lastmod: In the root listing view, show the most recent
## modifications made to the root.  (Subversion roots only.)
##
## NOTE: Enabling this feature will significantly reduce the
## performance of the root listing view.
##
#show_roots_lastmod = 0

But perhaps is a bug on Chromium. That much I certainly wouldn't know.