cache behavior for report-abuse/get_reviews
Bug #692561 reported by
Michael Vogt
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ratings and Reviews server |
Fix Released
|
Low
|
Michael Nelson | ||
Bug Description
When a package is flagged for moderation we should consider reseting the internal cache of the webapp to ensure subsequent requests for the app/pkg do not return it. Depending on my a review got flagged its important to ensure its not getting delivered (think of legal issues wit ha review).
Revision history for this message
| Michael Vogt (mvo) wrote | #1 |
| summary: |
- cache behavior for report-abuse + cache behavior for report-abuse/get_reviews |
| Changed in rnr-server: | |
| status: | New → In Progress |
| assignee: | nobody → Michael Nelson (michael.nelson) |
| importance: | Undecided → Low |
| Changed in rnr-server: | |
| status: | In Progress → Fix Committed |
| Changed in rnr-server: | |
| milestone: | none → 11.01 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I think it would be best if the webapp would control when to invalid the django caching. If a new review is coming in it knows that the cache needs to be updated, same for a abuse-report. So if we can tackle the problem at this layer, that would be perfect.