Delete query strings

[1v9]

A little bit of work 😎, if useless just close it.

[1v9]

I don't see docs of Assets...

[jiangtj]

v=version, this is to prevent browser caching...

[1v9]

@jiangtj Yes I know, just an option for some weird user like me.

[stevenjoezhang]

In fact, setting HTTP headers through the server is the most effective way to manage the cache...
I'm not sure this feature is necessary

[stevenjoezhang]

It's not necessary to use query string to prevent browser caching

$ curl -I https://mi.js.org/js/local-search.js?v=7.4.1
HTTP/2 200 
date: Fri, 18 Oct 2019 17:01:22 GMT
content-type: application/javascript; charset=utf-8
set-cookie: __cfduid=d79f075be4ed309369d4ef4cc2a84fdd31571418082; expires=Sat, 17-Oct-20 17:01:22 GMT; path=/; domain=.js.org; HttpOnly
last-modified: Tue, 01 Oct 2019 13:16:50 GMT
etag: W/"5d9351c2-2a5e"
access-control-allow-origin: *
expires: Fri, 18 Oct 2019 17:10:58 GMT
cache-control: max-age=600
x-proxy-cache: MISS
x-github-request-id: 0F14:1719:4EE10F:6760DC:5DA9EFC9
via: 1.1 varnish
age: 25
x-served-by: cache-lax8649-LAX
x-cache: HIT
x-cache-hits: 1
x-timer: S1571418083.740795,VS0,VE1
vary: Accept-Encoding
x-fastly-request-id: 95b96bf520e907134b77ef1652537e0ac7dbf58a
cf-cache-status: DYNAMIC
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 527c12e8f88776ce-LAX

$ curl -I https://theme-next.org/js/local-search.js?v=7.4.1
HTTP/2 200 
accept-ranges: bytes
cache-control: public, max-age=0, must-revalidate
content-length: 10814
content-type: application/javascript
date: Fri, 18 Oct 2019 17:02:17 GMT
etag: "a02f9d7291f8cfb99713dda481f3decb-ssl"
strict-transport-security: max-age=31536000
age: 0
server: Netlify
x-nf-request-id: 17a1c02e-1c5f-41f9-b6ca-dcdc1c28561b-1915334

[stevenjoezhang]

@jiangtj How do you like it?

[jiangtj]

是的，header可以设置缓存时间，但假如文件更新了（文件名不变），但缓存时间未到期，浏览器获取的文件是本地的缓存文件（旧），还是服务器端（新）的呢？

Yes, header can set the cache time, but if the file is updated (the file name remains the same), but the cache time does not expire, is the file obtained by the browser a local cache file (old) or server-side (new)？

[stevenjoezhang]

这两个例子中cache-control的时间都很短（0和600）。除非是用户自己用apache/nginx部署，并且把缓存时间设置为一个较大值（>1周），否则不会出现你说的情况。
目前这些服务商都会设置etag头，这样使用HTTP/2 + 304状态码效果明显好于query string。

[stevenjoezhang]

jsDelivr对于github资源的cache-control默认是一周

$ curl -I https://cdn.jsdelivr.net/npm/jquery/dist/jquery.min.js
HTTP/2 200 
date: Sat, 19 Oct 2019 19:03:32 GMT
content-type: application/javascript; charset=utf-8
content-length: 88145
access-control-allow-origin: *
access-control-expose-headers: *
timing-allow-origin: *
cache-control: public, max-age=604800, s-maxage=43200
x-content-type-options: nosniff
strict-transport-security: max-age=31536000; includeSubDomains; preload
etag: W/"15851-iFI5JDUbrAtdVg/gxXgeJVbnaT0"
accept-ranges: bytes
x-served-by: cache-ams21029-AMS, cache-hkg17920-HKG
age: 1
x-via: 1.1 VMtwzhdxjw169:4 (Cdn Cache Server V2.0), 1.1 VMtwzhdxnp201:1 (Cdn Cache Server V2.0)

cloudflare会继承用户设置，如果用作github.io的CDN服务，也有cache-control: max-age=600

[1v9]

So, provide an option, like long long ago I did...

[jiangtj]

这两个例子中cache-control的时间都很短（0和600）。除非是用户自己用apache/nginx部署，并且把缓存时间设置为一个较大值（>1周），否则不会出现你说的情况。
目前这些服务商都会设置etag头，这样使用HTTP/2 + 304状态码效果明显好于query string。

一旦本地缓存命中，不会请求服务器的，所以假如cache时间是一周，那么当你更新主题之后，你的博客用户可能在1周内遇到由于js或css未更新而导致的问题

[stevenjoezhang]

References:
https://developers.google.com/speed/docs/insights/LeverageBrowserCaching#LeverageProxyCaching
https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/http-caching#defining-optimal-cache-control-policy
https://web.archive.org/web/20140125154756/https://developers.google.com/speed/docs/best-practices/caching
https://web.archive.org/web/20141205221802/https://developers.google.com/speed/docs/insights/LeverageBrowserCaching

Google Developers

Leverage Browser Caching  |  PageSpeed Insights  |  Google Developers

Google Developers

HTTP Caching  |  Web Fundamentals  |  Google Developers

Caching and reusing previously fetched resources is a critical aspect of optimizing for performance.

Optimize caching - Make the Web Faster — Google Developers

Google Developers

Leverage Browser Caching

[1v9]

@stevenjoezhang @jiangtj Merge or not?

[jiangtj]

merge, 3 > 1 😂