title: Difference between ctrl-r, F5, and refresh button in Google Chrome
body: <p>I have an application which utilizes the janus-gateway to forward a gstreamer generated RTP stream to a vuejs client running in google chrome. Sometimes on page refresh the video is not displayed within the video element. The frequency with which this problem occurs varies depending on the method used to refresh the page. For instance ctrl-r works ~20 times without failing, while pressing the browser refresh button works only 2 times and then fails on every subsequent attempt. The "hard reload", and "empty cache and hard reload" options of the refresh button do not affect the frequency of the failure.</p>
  
  <p>When looking at the chome://webrtc-internals I see bandwidth coming into the browser. The janus-gateway admin api also indicated that it is sending the correct bandwidth. This leads me to think that the problem is related to resource binding within chrome.</p>
  
  <p>What is the difference between the ctrl-r, F5 and refresh button? Do they clear different resources?</p>
  
  <p>This behavior started in chrome version 71 and is not reproducible in chrome version 70 and earlier.  </p>