即使设置了 Cache-Control，动态生成的 CSS 文件也不会被缓存

发布于 2024-10-20 08:41:04 字数 747 浏览 2 评论 0原文

我有一个由 Spring 控制器动态生成的 CSS 文件。我在处理程序方法中设置了 Cache-Control 响应标头，但由于某种原因，我的 FireFox 在请求引用 CSS 文件而不是使用缓存版本时不断请求 CSS 文件。

这是代码。

@Controller
@RequestMapping("/foo.css")
public class FooController {
    @RequestMapping(method = RequestMethod.GET)
    public void show(HttpServletResponse response) {
        try {
            response.setHeader("Cache-Control", "max-age=3600");
            response.getWriter().println("this is a test.");
        }
        catch (IOException e) {
            e.printStackTrace();
        }

        System.out.println(new Date());
    }
}

HTML 文件以通常的方式引用 CSS 文件。

<link rel="stylesheet" type="text/css" href="/foo.css" />

我在这里做错了什么？

原文

I have a CSS file dynamically generated by a Spring controller. I set the Cache-Control response header in the handler method but for some reason my FireFox keeps requesting the CSS file when requesting an HTML file that has a reference to it instead of using the cached version.

Here's the code.

@Controller
@RequestMapping("/foo.css")
public class FooController {
    @RequestMapping(method = RequestMethod.GET)
    public void show(HttpServletResponse response) {
        try {
            response.setHeader("Cache-Control", "max-age=3600");
            response.getWriter().println("this is a test.");
        }
        catch (IOException e) {
            e.printStackTrace();
        }

        System.out.println(new Date());
    }
}

And the HTML file references the CSS file in the usual way.

<link rel="stylesheet" type="text/css" href="/foo.css" />

What am I doing wrong here?

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

对你再特殊 2024-10-27 08:41:04

我是OP，但经过进一步研究，我决定你需要自己实现这个。您需要让服务器生成 304 响应代码，以便客户端浏览器使用缓存资源，但 Spring 和 Tomcat 都不支持这种开箱即用的方式。

回复收藏 0 原文

酒绊 2024-10-27 08:41:04

首先，浏览器和代理服务器不需要遵守标头上的 HTTP 缓存控制。他们只是提供建议。也许浏览器忽略了缓存请求并遵循他的偏好配置。

另一种方法是将随机属性添加到由 javascript 生成的 url 中。类似于：

<link type="text/css" href="/foo.css?d=328943298432" />

这是一篇关于此主题的好文章 http://code.google .com/speed/page-speed/docs/caching.html

Well, first of all, browsers and proxy servers do not need to comply with HTTP Cache controls putted on the headers. They are only advisory. Maybe the browser is ignoring the cache request and obeying what is configured on his preferences.

Another way to do that is putting a random attribute to the url, generated by javascript. Something like:

<link type="text/css" href="/foo.css?d=328943298432" />

Here's a nice article about this subject http://code.google.com/speed/page-speed/docs/caching.html

回复收藏 0 原文

债姬 2024-10-27 08:41:04

Spring 支持这一点已经有一段时间了，并且在最近的版本中得到了改进。请参阅有关此的参考文档。

@Controller
public class FooController {

  @RequestMapping("/foo.css")
  public ResponseEntity<String> show() {

    String cssContent = generateCssContent();
    String version = hashCssContent(cssContent);

    // automatically writes CacheControl + Etag headers
    // generates HTTP 304 responses for conditional requests
    return ResponseEntity
        .ok()
        .cacheControl(CacheControl.maxAge(30, TimeUnit.DAYS))
        .eTag(version) // lastModified is also available
        .body(cssContent);
    }
}

This has been supported by Spring for quite a while now, and it has been improved in recent versions. See the reference documentation about this.

@Controller
public class FooController {

  @RequestMapping("/foo.css")
  public ResponseEntity<String> show() {

    String cssContent = generateCssContent();
    String version = hashCssContent(cssContent);

    // automatically writes CacheControl + Etag headers
    // generates HTTP 304 responses for conditional requests
    return ResponseEntity
        .ok()
        .cacheControl(CacheControl.maxAge(30, TimeUnit.DAYS))
        .eTag(version) // lastModified is also available
        .body(cssContent);
    }
}

回复收藏 0 原文

~没有更多了~