Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • erp5 erp5
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Merge requests 142
    • Merge requests 142
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedinexedi
  • erp5erp5
  • Merge requests
  • !1398

WIP: make AcceleratedHTTPCacheManager effective only if object is directly published.

  • Review changes

  • Download
  • Patches
  • Plain diff
Open Kazuhiko Shiozaki requested to merge limit_accelerated_http_cache_manager into master Apr 14, 2021
  • Overview 6
  • Commits 2
  • Pipelines 0
  • Changes 2

If we accidentally specify AcceleratedHTTPCacheManager in a widely-called Script (Python) by mistake (that happened in reality), many responses will have wrong Cache-Control header and it is very hard to recover if they are cached in each browser's cache.

With this change, AcceleratedHTTPCacheManager is effective only when the object itself is directly published, so that we can prevent such unexpected cache pollution.

/cc @romain @jerome @vpelletier @tb

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: limit_accelerated_http_cache_manager
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7