Home >Backend Development >Golang >Why Aren\'t My Edited Files Being Served by Go\'s FileServer Handler in Virtual Box?
Why Aren\'t My Edited Files Being Served by Go\'s FileServer Handler in Virtual Box?
- Mary-Kate OlsenOriginal
- 2024-11-03 02:52:29791browse
HTTP File Server Caching Issues
The net/http package in Go provides a FileServer handler for serving static files. However, users have encountered an issue where recently edited files are not being displayed, despite the Content-Length header in the response being accurate.
Cause:
The issue has been traced to using a Virtual Box shared folder to host the static files. When the files are accessed through the shared folder, Virtual Box performs caching, causing the outdated version of the file to be served by the FileServer handler.
Example:
Consider the following program:
package main
import (
"fmt"
"net/http"
)
func main() {
http.Handle("/", http.FileServer(http.Dir("./www/")))
err := http.ListenAndServe(":8080", nil)
if err != nil {
fmt.Println(err)
}
}
With the HTML file:
<code class="html"><!doctype html>
<html>
<body>
<p>Hello there everyone</p>
</body>
</html></code>
When accessing this page from the Vagrant box, the content will not be updated, even after refreshing the browser or modifying the HTML file.
Solution:
To resolve this issue, it is recommended to avoid using Virtual Box shared folders for serving static files with the http.FileServer handler. Instead, move the files to a local directory on the Vagrant box and serve them from there.
The above is the detailed content of Why Aren't My Edited Files Being Served by Go's FileServer Handler in Virtual Box?. For more information, please follow other related articles on the PHP Chinese website!