dongshan0202405 2013-12-20 11:05
浏览 72
已采纳

编辑后http.FileServer缓存文件并提供旧版本

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 demonstrate here is a simplified version of the application I am writing.

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)
    }
}

Now suppose we have a very simple html page:

<!doctype html>
<html>
<body>
    <p>Hello there</p>
</body>
</html>

I execute the go program and access http://localhost:8080 in the browser to be presented with:

Hello there

Checking the response headers I can see the following:

Status Code:200 OK
Accept-Ranges:bytes
Content-Length:68
Content-Type:text/html; charset=utf-8
Date:Fri, 20 Dec 2013 10:04:03 GMT
Last-Modified:Fri, 20 Dec 2013 10:03:32 GMT

Now I edit the html file so the <p> tag contains Hello there everyone and reload the page. I get the following:

Hello there

Again looking at the response headers I get

Status Code:200 OK
Accept-Ranges:bytes
Content-Length:77
Content-Type:text/html; charset=utf-8
Date:Fri, 20 Dec 2013 10:04:34 GMT
Last-Modified:Fri, 20 Dec 2013 10:04:14 GMT

So the Content-Length has changed as well as last modified but not the actual file content delivered by the http.FileServer handler. This issue happens even after closing the program down and doing go run src/.../main.go. The only way I have found so far to clear the apparently cached version of the file is to reboot the machine the program is running on.

I have tried the following:

  • Executing program on win / ubuntu / osx 10.8.5
  • Going through the chain of functions / interfaces on golang.org/src to see if the served file is cached on disk anywhere

Any help with this would be very much appreciated.

  • 写回答

4条回答 默认 最新

  • dotws86260 2014-01-11 14:31
    关注

    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.

    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论
查看更多回答(3条)

报告相同问题?

悬赏问题

  • ¥15 如何让企业微信机器人实现消息汇总整合
  • ¥50 关于#ui#的问题:做yolov8的ui界面出现的问题
  • ¥15 如何用Python爬取各高校教师公开的教育和工作经历
  • ¥15 TLE9879QXA40 电机驱动
  • ¥20 对于工程问题的非线性数学模型进行线性化
  • ¥15 Mirare PLUS 进行密钥认证?(详解)
  • ¥15 物体双站RCS和其组成阵列后的双站RCS关系验证
  • ¥20 想用ollama做一个自己的AI数据库
  • ¥15 关于qualoth编辑及缝合服装领子的问题解决方案探寻
  • ¥15 请问怎么才能复现这样的图呀