Skip to content
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

js: remove 301 redirect cache fix #363

Closed
wants to merge 1 commit into from
Closed

Conversation

tleb
Copy link
Member

@tleb tleb commented Dec 19, 2024

This code was required because we messed-up in the past regarding caching headers. This is not required anymore because the caching set has expired, so no well behaving user-agent should have remains.

This represents something like 240k requests to the backend (not the cache) over two weeks. Server load was minimal because generating those responses is really fast.

This code was required because we messed-up in the past regarding
caching headers. This is not required anymore because the caching set
has expired, so no well behaving user-agent should have remains.

This represents something like 240k requests to the backend (not the
cache) over two weeks. Server load was minimal because generating those
responses is really fast.

Signed-off-by: Théo Lebrun <[email protected]>
@tleb tleb requested a review from fstachura December 19, 2024 16:22
Copy link
Collaborator

@fstachura fstachura left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's time to remove this, I have nothing to add.

@tleb
Copy link
Member Author

tleb commented Jan 3, 2025

done in 972fdd7

@tleb tleb closed this Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants