Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set etag on pmtiles serve responses #137
Set etag on pmtiles serve responses #137
Changes from 4 commits
b373253
6f42f76
bac8bf4
f8d2c37
40d3b2d
68a0a74
99f7fc9
a1ac8b4
625b8d2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 1 in caddy/pmtiles_proxy.go
GitHub Actions / fmt_vet_lint
Check warning on line 18 in caddy/pmtiles_proxy.go
GitHub Actions / fmt_vet_lint
Check warning on line 47 in caddy/pmtiles_proxy.go
GitHub Actions / fmt_vet_lint
Check warning on line 60 in caddy/pmtiles_proxy.go
GitHub Actions / fmt_vet_lint
Check warning on line 87 in caddy/pmtiles_proxy.go
GitHub Actions / fmt_vet_lint
Check warning on line 1 in main.go
GitHub Actions / fmt_vet_lint
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The way I implemented this it also applies to metadata json and tilejson responses. Should I remove those? Or make this
--resource-etag
? or just leave it as-is?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also in my tests on a 32-core machine enabling this reduces throughput from 40k tiles per second to 36k tiles per second.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe
--unique-etags
instead, to make it clearer the effect?Check warning on line 75 in pmtiles/bucket.go
GitHub Actions / fmt_vet_lint
Check warning on line 85 in pmtiles/bucket.go
GitHub Actions / fmt_vet_lint