HTTP response fixes (increase cacheability) #67
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.
The 301 status means clients should never use the redirector to ask for a new mirror again, and direct all future requests to the one mirror they were redirected to on the first request. This is not what is intended here. A 307 temporary redirect is the correct response. Fixes #65.
Let clients and proxies cache responses from the redirector for 7:30 minutes instead of refetching the redirect from the redirector on every request within a short time frame. Makes the redirector play nicer with caching proxies who can handle mass-updates on a local network locally without refetching the remote resource for every request. Fixes #66.
See also my blog post.
Finally, add a Server header as it’s one of the few headers required by HTTP. Gave it the vanity name “http-redirector”.