go
/
htpack
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Efficient serving of pre-compressed static files.
18 Commits 1 Branch 35 Tags 116 KiB
Go 100%
Go to file
Laurence Withers 21a18eced6 cmd/packserver: use Cache-Control: no-cache 
Rather than setting "Cache-Control: no-store", use "no-cache". The
difference is that "no-store" tells the browser that it must always
completely re-fetch the resource; whereas "no-cache" means that the
browser can write the resource to disk but must re-validate it (e.g.
using Etags) before re-using it.
 		2019-04-25 14:47:13 +01:00
cmd cmd/packserver: use Cache-Control: no-cache 2019-04-25 14:47:13 +01:00
packed Reorganise ready to split into modules 2019-04-12 09:07:17 +01:00
.gitignore Finish up the initial packserver implementation 2019-04-15 14:10:26 +01:00
README.md Note a TODO in the README 2019-04-12 09:16:23 +01:00
go.mod Update dependencies 2019-04-15 14:15:43 +01:00
go.sum Update dependencies 2019-04-15 14:15:43 +01:00
handler.go Handler: add SetIndex 2019-04-25 14:17:55 +01:00

README.md

HTTP resource pack server

A common scenario is that you have a set of static resources that you want to serve up quickly via HTTP (for example: stylesheets, WASM).

This package provides a net/http-compatible http.Handler to do so, with support for:

  • compression
    • gzip
    • brotli, if you have the external compression binary available at pack time
    • does not yet support Transfer-Encoding, only Accept-Encoding/Content-Encoding
  • etags
  • ranges (TODO)

The workflow is as follows:

  • (optional) build YAML file describing files to serve
  • run htpacker tool to produce a single .htpack file
  • create htpack.Handler pointing at .htpack file

The handler can easily be combined with middleware (http.StripPrefix etc.).