Ctrl F5 doesn't erase the cache

I use the following, added to any links that need to be updated continuously, mainly PDF files where changing the name of the file isn't an option (which is the best way to avoid caching). It seems to defeat Chrome's latest caching behavior in all of my testing...

onClick="this.href=this.href.split('?')[0]+'?'+new Date().getTime()"

The final link code would look like...

<a href="calendar_2017.pdf" onClick="this.href=this.href.split('?')[0]+'?'+new Date().getTime()">

The code adds a unique query string onto the end of any link it's attached to when clicked. That has the effect, in the vast majority of browsers, of tricking the browser into downloading a new copy on each click. Because the code uses the href already in the link tag, it will continue to work as normal if .js is turned off in the viewer's browser, though cache would kick in normally as well.

Adding to Nancy's reply, Chrome has a relentless caching system, a feature that other browsers will undoubtedly follow in the interests of greater efficiency.

I feel that we, as developers, need to accommodate the sticky cache by using cache busting techniques For more info, Google Cache Busting

Some browser's like Chrome have a sticky cache or browsing data history.  The only reliable way to clear the cache is through your browser settings.

Clear cache and cookies - Computer - Google Account Help

Nancy