No description
Find a file
Nugraha e5eab664d3
All checks were successful
continuous-integration/drone/push Build is passing
ci: initial files
2022-12-06 18:15:25 +07:00
.config all: initial files 2022-12-05 03:48:53 +07:00
.github/workflows ci: initial files 2022-12-06 18:15:25 +07:00
.vscode all: initial files 2022-12-05 03:48:53 +07:00
docker docker: varnish cache purge, and cache indicator 2022-12-05 19:46:59 +07:00
.dockerignore all: initial files 2022-12-05 03:48:53 +07:00
.drone.yml all: initial files 2022-12-05 03:48:53 +07:00
.env.example all: initial files 2022-12-05 03:48:53 +07:00
.gitignore all: initial files 2022-12-05 03:48:53 +07:00
.goreleaser.yml ci: initial files 2022-12-06 18:15:25 +07:00
Dockerfile all: initial files 2022-12-05 03:48:53 +07:00
go.mod all: initial files 2022-12-05 03:48:53 +07:00
go.sum all: initial files 2022-12-05 03:48:53 +07:00
LICENSE all: initial files 2022-12-05 03:48:53 +07:00
main.go all: initial files 2022-12-05 03:48:53 +07:00
Makefile ci: initial files 2022-12-06 18:15:25 +07:00
obs.go all: initial files 2022-12-05 03:48:53 +07:00
obs_test.go all: initial files 2022-12-05 03:48:53 +07:00
README.md ci: initial files 2022-12-06 18:15:25 +07:00
server.go all: initial files 2022-12-05 03:48:53 +07:00
util.go all: initial files 2022-12-05 03:48:53 +07:00
util_test.go all: initial files 2022-12-05 03:48:53 +07:00

obs-access-signer

S3 Object Storage access signer.

Run obs-access-signer behind a gateway/cache proxy is preferred as the response is static.

There's an example of using it with Varnish Cache, which you can see here.

Why?

Some S3-compatible gateways might not support ACL endpoints but they support presigned access. Currently, the behavior of obs-access-signer is similar to public-read ACL where clients can access objects anonymously and redirect them (permanently) to presigned URL with Expires set to the max signed value of int64 which has roughly 250yrs lifetime since UNIX time started.

License

Apache-2.0