-
Notifications
You must be signed in to change notification settings - Fork 79
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
MCS: Stop using storage for wiktionary definitions #1181
Conversation
@@ -150,35 +100,7 @@ paths: | |||
content-type: '{{extract.headers.content-type}}' | |||
vary: '{{extract.headers.vary}}' | |||
body: '{{extract.body}}' | |||
- emit_change_event: |
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 response_cache_control
here will still be pretty long. We need to either return some kind of purging or make much smaller cache max-age
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.
In the CP config patch we keep the purging side of things, so this will not be an issue.
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.
No. If you don't emit the resource-change for this route, no purge will be emitted.
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.
Indeed, I'll add a purge event to the CP config, that ought to fix it.
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.
@Pchelolo updated the CP config patch to reflect what we discussed here
c9c19b9
to
f4f84e2
Compare
+1, waiting for travis |
Bug: T231361