http.FileServer caching files and serving old versions after edit

Question

Having issues with the http package in the core of go. It appears that the file contents is cached although the Content-Length in the response body is correct. To demonstrat

Answer 1

Ok, so after a few weeks of ignoring the problem and moving on I have finally worked out what the issue is.

In order to leave my main computer fairly uncustomised I use Vagrant to develop applications using golang, nodejs and php. It appears that running a go application on a Virtual Box share with all the html files stored on that share causes this issue.

To prove this I span up a Vagrant box and copied the files from the /vagrant shared directory to /home/vagrant/testing/, then replicated all the previously listed actions. This made the problem disappear.

So in other words, don't use a Virtual Box shared folder to host files intended for use in a http.FileServer method.