Better caching #794
No reviewers
Labels
No labels
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#794
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "better-caching"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Based on @trinity-1686a's patch.
I'm not sure it is a fix for #786 but it is better than nothing.
OK, my git history is broken, I need to fix that.
🙋️
@ -67,1 +67,4 @@
// NGINX (and maybe other software) sometimes sends ETags with a
// "W/" prefix, that we ignore here
.any(|s| s[1..s.len() - 1] == etag || s[3..s.len() - 1] == etag)
{
can one of you two explain what this does?
don't we still have to to change the subscribe/follow/blah button from a form… to… well… a button?
@ -67,1 +67,4 @@
// NGINX (and maybe other software) sometimes sends ETags with a
// "W/" prefix, that we ignore here
.any(|s| s[1..s.len() - 1] == etag || s[3..s.len() - 1] == etag)
{
this should probably get it's comment actually.
We send Etags as
'some_tag'
, the old match does not verify the'
, but check that whatever in-between is the right tag. Nginx apparently change the Etag toW/'some_tag'
, W/ indicating it's a weak Etag, the content may not be byte-equal, but is semantically identical (which is imo a shitty but correct interpretation of the RFC, as Nginx send compressed data)The new match ignore that W/ saying it's a weak etag and so match if Nginx modified the header we sent previously
Comment might looks like : // if a strong or weak etag matches
well there is that too, but these buttons are not here on the front page or a blog or user page. Anyway for post a better caching solution that does not require to query the database should be added
Codecov Report
Merged into
main
branch as #840Pull request closed